I agree that the impeding JAX-WS stub generation will resolve this
non-standard dependency issue. But going back and looking at my
comments, my whole point was that Axis2 does not currently support the
standard Java APIs (JAX-RPC or JAX-WS). As soon as Axis2 adds support
for JAX-WS, this whole
In fact any databinding framework in Axis2 relies on AXIOM. Take a
look at the generated stubs/skeletons. They are indeed XML Beans or
JAXB specific, but all of them use AXIOM behind the hood. This means
you have a dependency on axiom, regardless of the databinding you
choose.
fromOM(...),
I don't really agree with Anne's point. If you use the current Axis2
WSDL2Java then you are tied to Axis2's current stub model (which is
pretty POJO like). But inside those stubs you can use
JAXB/JIBX/XMLBeans, all of which isolate you from AXIOM.
Were you to choose a different stack, your data
-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 09, 2007 7:43 PM
To: axis-user@ws.apache.org
Subject: Re: consequences of choosing axis
Yes. Axis2 communicates via SOAP, and supports reasonable
interoperability with any other web services platform that communicates
via
Subject: Re: consequences of choosing axis
Yes. Axis2 communicates via SOAP, and supports reasonable
interoperability with any other web services platform that communicates
via SOAP. That is not the issue or consequence I'm talking about.
If the client is implemented using AXIOM, then it is tied
To: axis-user@ws.apache.org
Subject: Re: consequences of choosing axis
Yogen,
That is your opinion, and you're welcome to it. But that's because
JAX-RPC and JAX-WS compliance isn't important to you.
But let me give an example of where it might be important.
Let's say you purchase a piece of software
@ws.apache.org
Subject: Re: consequences of choosing axis
Sorry for being vague. I was referring to the SOAP platform, not the
underlying servlet/J2EE platform. As I said, Axis2 can be deployed on
any platform. But AXIOM is particular to Axis2. (It is a separate
project, and other SOAP
Anne,
One consequence of selecting Axis2 is that it does not [yet] support
the standard Java APIs for web services (JAX-RPC and JAX-WS). Axis2
uses a platform-specific object model, AXIOM, which is based on StAX,
for processing XML. For the most control, you can use the low-level
API, which
Sorry for being vague. I was referring to the SOAP platform, not the
underlying servlet/J2EE platform. As I said, Axis2 can be deployed on
any platform. But AXIOM is particular to Axis2. (It is a separate
project, and other SOAP platforms could use it, but to date, the only
other project that I
with AXIOM on the server side.
HTH
-yogen
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 09, 2007 6:58 PM
To: axis-user@ws.apache.org
Subject: Re: consequences of choosing axis
Sorry for being vague. I was referring to the SOAP platform
@ws.apache.org
Subject: RE: consequences of choosing axis
Clients don't have to use AXIOM. Clients could construct a WS-I
compliant SOAP message whichever way they can, .Net, C++ or Perl clients
would do this.
Since JAXB and other databindings are supported, server side need not
use AXIOM either. Only
if you choose no-databinding, you would be
dealing with AXIOM on the server side.
HTH
-yogen
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 09, 2007 6:58 PM
To: axis-user@ws.apache.org
Subject: Re: consequences of choosing axis
Sorry for being
Anne,
Thanks. The comparison to other frameworks makes this perfectly
clear, almost to the duh point. By proprietary you don't mean non
open source do you? Just non-standard?
Chad
The fact that Axis2 supports a variety of databinding frameworks does
not change the fact that it does not
Yes -- non-standard.
On 1/9/07, ChadDavis [EMAIL PROTECTED] wrote:
Anne,
Thanks. The comparison to other frameworks makes this perfectly
clear, almost to the duh point. By proprietary you don't mean non
open source do you? Just non-standard?
Chad
The fact that Axis2 supports a variety
Anne,
FYI, Spring-WS supports AXIOM too.
thanks,
-- dims
On 1/9/07, Anne Thomas Manes [EMAIL PROTECTED] wrote:
Sorry for being vague. I was referring to the SOAP platform, not the
underlying servlet/J2EE platform. As I said, Axis2 can be deployed on
any platform. But AXIOM is particular to
Chad,
On 1/6/07, ChadDavis [EMAIL PROTECTED] wrote:
Hi. I'm jut getting started learning about web services, and I've
decided to use axis2. I'm trying to figure out whether this choice
incurs any consequences. I could have chosen from several other
platforms that support web service
Good Evening Chad
No consequences as long as you're willing to put in the effort to determine
which version you're going to use, build the examples/samples and modify the
sample to suit the features you desire
The service and the client will have to agree on style (RPC or doc/literal),
Hi Chad,
I might not be the best person to answer this, but here's how I see it..
if a web service publishses a WSDL, then the client could be built on
any web service technology that works with WSDL -- correct?
Yes..Exactly.. That's how it works most of the times..
But to be honest, there can
18 matches
Mail list logo
