Hi Thomas/All, Thanks for the useful response. I appreciate it!
If I moves axis w/ document or wrapped style of implementation from soap w/ messagerouter implemenation, do the clients need to be changed? We have 2 kinds of clients - web and windows - invoking the soap services. I do not mind changing the server side soap code to any extent, but maintaining backward compatibility with respect to client is our requirement in this migration. I think I was (still a little bit) confused w/ the available styles of services in axis. Axis site http://ws.apache.org/axis/java/user-guide.html lists a few styles and other sites list few other styles. I found the following site useful regarding styles in axis: http://www.javaworld.com/javaworld/jw-10-2003/jw-1003-wsstyles.html. Though, since Axis site does not explain anything about doc-lit style, I am not sure if doc-lit style is a style officially declared by apache, or just a term used by people. I would appreciate any input. Pramodh Peddi Software Engineer v 781-674-2738 f 781-674-2760 www.imprivata.com People are talking about OneSign: "We were spending 35% of our IT time on password-related issues, says Paula Chesbrough, CIO of Eagle Bank in Everett, Mass. "We've reduced that workload to 10%." Network World, 8/9/04 "Imprivata Quells Management Burdens" CRN, 8/9/04 -----Original Message----- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 5:23 PM To: [EMAIL PROTECTED] Subject: Re: Famous "Migration from Soap to Axis" problem I can't definitively answer your basic question regarding performance, but based on anecdotal evidence, I expect you to experience a 5x or better performance improvement when switching from SOAP to Axis. The article you cited regarding Axis doc/literal and DOM refers only to the Axis "message" style. If you use "wrapped" or "document" style, then Axis uses SAX to automatically transform XML into Java objects. Unfortunately, you will need to rewrite your application code that currently uses the SOAP Message router. - Anne On Fri, 7 Jan 2005 14:24:43 -0500, Pramodh Peddi <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > I was reading through the archives, but no one seems to have a reasonable > answer from anyone for many people's problem/question "Migration from Apache > Soap to Apache Axis". I was also googling for any document to help me in > this task, but could not find anything useful. I wish > http://ws.apache.org/axis/ site came up with one such a document knowing > that so many people are having problems during migration. Well, if I can > find anyone who can answer my questions, I will feel very happy and I would > appreciate. > > > > My first question is: Does migration from Soap to Axis give us any > performance benefits? I know that Axis internally uses SAX implementation as > opposed to Soap using DOM, which might give us memory and time performance > benefits. But reading few articles raised few questions in my mind on this > (see below link). > > > > My company is planning to migrate from Apache SOAP 2.3 to Apache Axis1.1, > mainly to get any performance benefits from Axis. We use Message router > implementation. When we use RPC router, migration from Soap to Axis is > relatively easy, because rpc router implementation does not use any soap > specific classes in the code. So, it is literally replacing the soap jars > with axis jars. But, when using message router, we use many soap specific > classes like org.apache.soap.SOAPContext, org.apache.soap.Envelope, > org.apache.soap.Body, etc. Since Axis does not support these classes, we > have to change the code. And this is as much as I know, am sure there is > more to that. Is there any other way? > > > > What is the best style of encoding? We are planning to use doc-lit style > when moving to Axis (as I heard good things about doc-lit style). When I was > googling, I came through an article comparing the performances of different > styles. Following is the article. It says "The current implementation of > document-literal web services with Axis always returns the DOM structure of > the incoming message directly to the business module." This is scary, > because the whole point is to NOT use DOM objects while reading the request > xml. Is this really true? > > http://www.phptr.com/articles/article.asp?p=177376&seqNum=7 > > "However, there is one major flaw in the Axis document-literal web services > that might compel you to consider web services with attachments. The current > implementation of document-literal web services with Axis always returns the > DOM structure of the incoming message directly to the business module. > There's no way to retrieve the message as a string and bypass the DOM > creation." > > > > Finally, after moving to Axis, does the client code need to be changed? For > us, it is important that client code does not change due to backward > compatibility requirement - because old clients (currently used by > customers) need to be able to talk to new server. > > > > Thanks in advance. > > > > Pramodh. > > > > > > > > Pramodh Peddi > > Software Engineer > > v 781-674-2738 > > f 781-674-2760 > > www.imprivata.com > > > > People are talking about OneSign: > > "We were spending 35% of our IT time on password-related issues, says Paula > Chesbrough, CIO of Eagle Bank in Everett, Mass. "We've reduced that workload > to 10%." Network World, 8/9/04 > > > > "Imprivata Quells Management Burdens" > > CRN, 8/9/04 > >
