| 
      
      
      From: Bruce M. <br...@mc...> - 2003-04-07 13:06:16
      
     | 
| Hans, Unfortunately this pipelinestage has not recieved all the attention that other stages have. I would welcome suggestions as to how to address these kinds of issues. regards, Bruce. On Monday 07 April 2003 07:55 am, Hans Benedict wrote: > Hi, > > I have just started experimenting with the SoapWriterPipelineStage. > I wanted to find out, what happens to the Messages when something goes > wrong. > > To my surprise I found, that I do not get any Exceptions when there are > HTTP Errors like 404 (e.g. due to misspelled URL) or 500 (e.g. due to > calling the wrong SOAP function: > [from the SOAP response: ...] > <env:Fault><faultcode>env:Server</faultcode><faultstring>Internal Server > Error (unrecognized operation: nitf)</faultstring></env:Fault> > [...]). > > Is this the normal behaviour? > > Btw: I *do* get an Exception when the connection is completely refused: > Error: com.babeldoc.core.pipeline.PipelineException: Error sending soap > message: Error opening socket: java.net.ConnectException: Connection > refused > > So to me it looks like org.apache.soap.messaging.Message does not throw an > Exception where I am expecting it - am I missing something? > > Regards, > Hans > > > > ------------------------------------------------------- > This SF.net email is sponsored by: ValueWeb: > Dedicated Hosting for just $79/mo with 500 GB of bandwidth! > No other company gives more support or power for your dedicated server > http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |