Hi Wolfgang,
first off, thanks for both responses to my postings - very informative
and I appreciate it.
Regarding your response below, my original posting said "the Axis
project implements a standard", which
is in a agreement of what you are also saying below - implementation
engines do not and SHOULD NOT
create standards - of course ;). And since we both agree on that then if
you are right that
theoritically the SOAP message structure does not get changed across
versions of Axis then that;s what
I needed to know. Now I wouldn't have needed to bother with SOAP at all,
but there was a reason
I asked the Q - in a design I am working on we intercept, inspect and
modify the outgoing and incoming
SOAP messages to offer a configurable addressing scheme. I am sure there
are a few other ways to do this but
I am following requirements. So if my legacy design needs to be changed
once I upgrade to Axis because
of the SOAP message it would be good to know beforehand - I will follow
up in practice with this
and let you know what I find.
Thanks much
WJ Krpelan wrote:
Hi,
Webservice Engines dont create Standards but try to implement them - as good as
it gets anyhow -
I'd say developers of Web Services should not need to bother with SOAP at all
- apart from extreme cases of interoperability problems.
Using a WSDL first approach you should have no problems exchanging your Web
Service Engine on one ore both sides - that is, theoretically
To answer your question literally - no, I dont think so!
Cheers, Wolfgang
--- On Thu, 8/27/09, Demetris <demet...@ece.neu.edu> wrote:
From: Demetris <demet...@ece.neu.edu>
Subject: SOAP message structure
To: axis-dev@ws.apache.org
Date: Thursday, August 27, 2009, 10:17 PM
In our migration from the Axis 1.x to Axis2 and beyond, one
question that came up was how the SOAP
message structure emitted by the client stubs generated by
Axis2 is exactly the same as the one that would
have been created for the same Web Service from an Axis 1.x
stub (considering the same encoding styles).
I know the Axis project implements a standard so I am
expecting that it still follows that standard across
versions - if it offers async invocations or all the other
goodies that is a separate layer, but the emitted
SOAP messages I am not expecting to change. Is that a
correct assumption?
Thanks
