CXF - General questions

[mahendran <ma...@wachovia.com>]

Hi,
I work for a large banking firm. We are currently in the process of
upgrading our application server stack and associated services. We are
looking to integrate Spring and web services across different platforms. Our
aim is to deploy components that are Spring based but expose them to
non-java clients as web services.
We tried using Spring's native web services component which worked fine with
java clients. With non-java clients we found that JAX-WS worked better. So
this brings us to CXF which supports JAX-WS and Spring. We were able to
follow the examples in the Apache CXF site and get some POCs running. But we
do have some questions.

1. Does CXF have plans to upgrade to the latest versions of JAX-WS? What
happens when JAX-WS 2.0 comes out?
2. We are also looking into JAX-WS RI for the same purpose? Have anyone
tried that? If so how does it compare against CXF?

I'm fairly new to this subject, so I would appreciate any kind of
suggestions.
Thanks
-- 
View this message in context: http://www.nabble.com/CXF---General-questions-tf3884558.html#a11010279
Sent from the cxf-user mailing list archive at Nabble.com.

Re: CXF - General questions

[Daniel Kulp <dk...@apache.org>]

On Thursday 07 June 2007 11:30, mahendran wrote:
> Hi,
> I work for a large banking firm. We are currently in the process of
> upgrading our application server stack and associated services. We are
> looking to integrate Spring and web services across different
> platforms. Our aim is to deploy components that are Spring based but
> expose them to non-java clients as web services.
> We tried using Spring's native web services component which worked
> fine with java clients. With non-java clients we found that JAX-WS
> worked better. So this brings us to CXF which supports JAX-WS and
> Spring. We were able to follow the examples in the Apache CXF site and
> get some POCs running. But we do have some questions.
>
> 1. Does CXF have plans to upgrade to the latest versions of JAX-WS?
> What happens when JAX-WS 2.0 comes out?

Currently, CXF is targeting JAX-WS 2.0 mostly due to demands from various 
integrators and other applications like Geronimo that require a JAX-WS 
2.0 solution for their J2EE5 certifications.   For a report on the 
status of that:
http://netzooid.com/blog/2007/06/05/cxf-is-jax-ws-certified-in-geronimo-20-m6-rc1/
which should give you an indication of how close we are.   :-)

Once we have a "released" version of CXF that meets the 2.0 demands, 
we'll most likely start working on the additions that were added for 2.1 
in hopes that CXF 2.1 will be JAX-WS 2.1 compliant.   


> 2. We are also looking into JAX-WS RI for the same purpose? Have
> anyone tried that? If so how does it compare against CXF?

Chris explained some of the differences fairly well from basic SOAP and 
Spring points of view.   Basically, if all you are interested in is a 
basic SOAP/HTTP solution, JAX-WS RI works fine if you are OK with it's 
Spring integration.   However, CXF provides a lot of extra stuff that 
the RI doesn't.   We have support for things like WS-RM, WS-Security, 
some WS-Policy, some failover functionality, much better HTTPS support, 
I think better JMX management, etc...

Of course, with CXF, you also have Apache Licensed source code and a 
growing Apache community behind it.    Some people find that valuable.  

:-)


-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194
daniel.kulp@iona.com
http://www.dankulp.com/blog

RE: CXF - General questions

[Christopher Moesel <Ch...@avid.com>]

I have used both CXF and JAX-WS RI.  While both are good solutions, I
prefer CXF for its ease of use, flexibility, and extendibility.  While
JAX-WS RI is also flexible and extendible, I find CXF to feel more
natural in the way that it is done.  

As for Spring integration, CXF treats Spring as a 1st class citizen-- it
has been an important part of CXF from the very beginning.  JAX-WS RI,
on the other hand, added Spring support later in its development cycle
in response to user requests.  I think that this is actually fairly
apparent in its usage.

But in all honesty (IMHO, anyway), you can't go wrong with either one.
I just happen to think you'll go better with CXF. But I may be biased as
a former XFire user. ;)

As for JAX-WS 2.0, I'm not sure I understand your question.  JAX-WS 2.0
*is* already out, and *is* supported by CXF.

-Chris


-----Original Message-----
From: mahendran [mailto:mahendran.sreedevi@wachovia.com] 
Sent: Thursday, June 07, 2007 11:31 AM
To: cxf-user@incubator.apache.org
Subject: CXF - General questions


Hi,
I work for a large banking firm. We are currently in the process of
upgrading our application server stack and associated services. We are
looking to integrate Spring and web services across different platforms.
Our
aim is to deploy components that are Spring based but expose them to
non-java clients as web services.
We tried using Spring's native web services component which worked fine
with
java clients. With non-java clients we found that JAX-WS worked better.
So
this brings us to CXF which supports JAX-WS and Spring. We were able to
follow the examples in the Apache CXF site and get some POCs running.
But we
do have some questions.

1. Does CXF have plans to upgrade to the latest versions of JAX-WS? What
happens when JAX-WS 2.0 comes out?
2. We are also looking into JAX-WS RI for the same purpose? Have anyone
tried that? If so how does it compare against CXF?

I'm fairly new to this subject, so I would appreciate any kind of
suggestions.
Thanks
-- 
View this message in context:
http://www.nabble.com/CXF---General-questions-tf3884558.html#a11010279
Sent from the cxf-user mailing list archive at Nabble.com.