Menu
▾
▴
Re: [Babeldoc-devel] SOAP: missing Exceptions
|
From: Bruce M. <br...@mc...> - 2003-04-11 17:44:25
|
See you on monday - Schoene Wochende! On Friday 11 April 2003 01:37 pm, Hans Benedict wrote: > Erik, > > if you want to take another look, here are now all classes of the soap > module ported to jaxm. You will need the libraries I sent before. > > Bruce and Dejan didn't have any objections against using the new api, so > I think I will commit this on monday, after some more testing. > (It's 19:30 now here, and time for the weekend... :-) ) > > Regards, > Hans > > On Fri, 11 Apr 2003 ek...@ba... wrote: > > Thanks so much. I will let you know what I find. > > > > Also, has it been decided that this SoapWriterPipelineStage will be > > ported to JaxM/saaj and included in Babeldoc, or is this just your > > modification for your personal use? > > > > Erik > > > > > > > > To: ek...@ba... > > cc: > > Subject: Re: [Babeldoc-devel] SOAP: missing Exceptions > > > > > > Erik, > > > > I do have a version of SOAPWriterPipelineStage that is ported to > > jaxm/saaj (and a little bit of dom4j). I is better in a way that it > > throws an exception when encountering a 404 error, but so far has no > > additional features. > > > > I didn't want to put it into CVS bevore the next RC, but in case you are > > interested, I have attached a zip with the new version and the libraries > > it uses to this mail (paths in the zip start at modules/soap). > > > > I am looking forward to any comments. > > > > Regards, > > Hans > > > > On Thu, 10 Apr 2003 ek...@ba... wrote: > > > Hans, > > > > > > I was wondering if you made any progress on modifying the > > > SOAPWriterPipelineStage ... I was planning on using it for a > > > Proof-of-Concept test on Friday and thought that if you had a "better" > > > working version, you might want to share it with me. I noticed that > > > you haven't placed into CVS. Please let me know. Thanks. > > > > > > Erik Klein > > > > > > > > > > > > Sent by: bab...@li... > > > To: Hans Benedict <ben...@ch...> > > > cc: bab...@li... > > > Subject: Re: [Babeldoc-devel] SOAP: missing Exceptions > > > > > > > > > Hans, > > > > > > This is a trick question. The first thing to do is to make you a > > > developer. > > > I am on this now. You will have to get your SSH public key uploaded > > > to sourceforge. Now as to the question of changing the SOAP library - > > > > heres > > > > > my > > > thinking: (This email has been written in stages) > > > > > > This sounds good. Thanks for you efforts here. Please make the > > > > change > > > > > but > > > bear in mind that if you change the "SOAP library" from apache's to > > > > sun's > > > > > then you will have to touch other code too. You will have to be sure > > > that > > > you can do it all before you start a wholesale rewrite. > > > > > > > > > regards, > > > Bruce. > > > > > > On Tuesday 08 April 2003 08:50 am, Hans Benedict wrote: > > > > 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 > > > > > > > > > > > > _______________________________________________________________________ > > >_ The information in this e-mail, and any attachment therein, is > > > > confidential and for use by the addressee only. If you are not the > > intended recipient, please return the e-mail to the sender and delete it > > from your computer. Although The Bank of New York attempts to sweep > > e-mail and attachments for viruses, it does not guarantee that either are > > virus-free and accepts no liability for any damage sustained as a result > > of viruses. > > > > > > > > > > > > > > ________________________________________________________________________ > > The information in this e-mail, and any attachment therein, is > > confidential and for use by the addressee only. If you are not the > > intended recipient, please return the e-mail to the sender and delete it > > from your computer. Although The Bank of New York attempts to sweep > > e-mail and attachments for viruses, it does not guarantee that either are > > virus-free and accepts no liability for any damage sustained as a result > > of viruses. |
