Re: [Babeldoc-devel] Babeldoc soap support question(s)

[David G. <dg...@co...>]

Hi Jonathan,

I've modified SoapWriterPipelineStage to match HttpClientPipelineStage in how 
it handles response documents (I've also added a boolean option responseDoc 
that defaults to false, so that the old behavior is maintained).  However, 
I'm not sure how to actually USE the response document in a pipeline.  Would 
you have a snippet of your config file where you set up the 
HttpClientPipelineStage and the following stage(s) that process the response 
that I could review?


Thanks for your help,

David


On Wednesday 06 August 2003 10:09 am, David Glick wrote:
> Thanks for the pointer, Jonathan.  I'm reviewing it now.
>
> On Wednesday 06 August 2003 9:50 am, Leech, Jonathan wrote:
> > I'm not sure about all the details of SOAP, but I just wrote an
> > HttpClientPipelineStage that's pretty generic, and it makes a document
> > out of the reply.  You might want to take a look at it, its located in
> > the web module.
> >
> > -Jonathan
> >
> > -----Original Message-----
> > From: David Glick [mailto:dg...@co...]
> > Sent: Wednesday, August 06, 2003 10:52 AM
> > To: bab...@li...
> > Subject: [Babeldoc-devel] Babeldoc soap support question(s)
> >
> >
> > I'll be building an interface to a soap web service API, and therefore I
> > thought I should stop futzing around and actually look into building the
> > pipeline.  In starting to review the soap stuff, I've come across the
> > some issues that I would appreciate those with years of experience (or
> > even weeks
> >
> > will work) to comment on.
> >
> > I need to go through a (relatively) complicated process as follows:
> >
> > a. post soap document.  Response is either transaction id or failure
> > code. b. if transaction id, post soap queries for status of transaction
> > until status
> > = done.
> > c. if failure code, indicate failure through some magic that I haven't
> > thought
> > of yet.
> >
> > I have the following questions:
> >
> > 1. The current soap writer ignores the reply.  I'll need to change that,
> > but
> >
> > I'd like to implement it such that it can be as generic as possible.  Is
> > there a description somewhere of how a stage writer should act?  Or,
> > lacking
> >
> > that, which is the best stage writer to use as a template for how the
> > SoapWriter should be modified?
> >
> > 2. How should the reply be handled?  Is there some current stage that I
> > can use, or will I need to create my own stage to process the reply?  If
> > I need to roll my own, is there some guide lines to make it generic for
> > general use,
> > or should I just make it specific to my needs?
> >
> >
> > Thanks,
> >
> > David

-- 
David Glick
Transmit Consulting, Inc
619-475-4052
dg...@tr...