|
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 People are talking
about OneSign: “Imprivata
Quells Management Burdens” |
<<image001.gif>>
