| 
      
      
      From: Bruce M. <br...@mc...> - 2003-04-08 14:24:55
      
     | 
| On Tuesday 08 April 2003 09:24 am, Dejan Krsmanovic wrote: > Hans, > My opinion is that you should make your changes. soap is module that will > be used by less users than core. Also, it has not been tested a lot anyway. > So if you think we could make these things work correcty my advice is "just > do it!". > Pipeline stage and saop feeder servlet are separate parts of application > and using of first does not imply using of others. I want to say that it is > not too important that they should use same libraries if it is hard to > change servlet. > > Dejan > > P.S. > Bruce, you should add Hans to developers list. He has already done few > bugfixes and I think he will be helpful in the future, too. (Am I right, > Hans?! ;-) ) Done. Dejan is correct here - the soap module has not been extensively tested but I certainly think that the feeder and the pipeline should use the same library. > > ----- Original Message ----- > From: "Hans Benedict" <ben...@ch...> > To: "Bruce McDonald" <br...@mc...> > Cc: <bab...@li...> > Sent: Tuesday, April 08, 2003 2:50 PM > Subject: Re: [Babeldoc-devel] SOAP: missing Exceptions > > > On Mon, 7 Apr 2003, Bruce McDonald wrote: > > > 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. > > > > Bruce, > > > > I took some time reading the sources of Apache SOAP. The http status is > > read somewhere down in org.apache.soap.util.net.HTTPUtils and then > > ignored. So it is not accessible from the point where you call > > the send method of org.apache.soap.messaging.Message. And even the > > parsing of the (html) error message of the server does not lead to an > > SOAPException. > > > > The only way I see to fix this, is to use another SOAP API. My suggestion > > is to switch to Sun's JAXM/SAAJ API, which throws a SOAPException when > > encountering an 404 error. The rewrite of the SOAPWriterPipelineStage > > should not be to difficult, but I have not yet looked at the two other > > classes. Is any of the other modules using the SOAP API? > > > > Concerning real SOAP faults, it seems that the client, i.e. the > > pipelinestage, has to check the SOAP response for them, and then throw an > > Exception by itself. > > > > If you agree, I could do the rewrite as well as the additional fault > > handling. But probably you don't want to have too many changes before the > > 1.0 release... Maybe, we should only add the fault handling and keep the > > rewrite for later? > > > > 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 > > ------------------------------------------------------- > 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 |