[jbossws-dev] Re: JBoss web services versus AXE?

[Thomas Diesler]

Hi Rob,

Is "Apache Web Services" the Axis stack?

http://ws.apache.org/axis2/

If so, it is because Axis is the worst stack out there, which is also
far from beeing a JavaEE5 certified stack.

A more valid question would be why do we not ship with the Sun RI
(https://jax-ws.dev.java.net/) or XFire (http://xfire.codehaus.org/)
both of which are more feature complete and stable than Axis.

The problem with XFire is that it is not (yet) JavaEE5 certified and
does not (and will not) support JAXRPC. 

The Sun RI is certified but also does not support JAXRPC but recently
has made good progress and provides support for a number of WS-*
specifications.

For future direction we plan that JBossWS uses both of these stacks as
the underlying engine. So you will be able to run

JBossWS: 	AS50, AS42, AS40, TC55
JBossWS-RI:   	AS50, AS42, AS40, TC55
JBossWS-XF:   	AS50, AS42, AS40, TC55

This is planed for jbossws-2.1.0 (01-Sep-2007)

Bottom Line: If you care about interoperability use a certified stack,
which Axis is not.

cheers
-thomas




On Thu, 2007-05-10 at 13:29 -0400, Robert Greathouse wrote:
> Hi,
> 
> I have a client who wanted to know why we did not include the Apache Web 
> Services and instead built our own.
> 
> The real question is for compatibility.  The want to be able to write 
> portable Web Services applications that can run on other App Servers.
> 
> This is Telcordia and we are looking for ways to jam our foot in the 
> door.  So a good story on our portability would be nice.
> 
> Robb,
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx