We're actually already using the jax-ws annotations and are only using
axis2 as a ready-to-go war implementation. Not sure why we picked axis2,
cxf should work too.
It looks like Jeff found a way to make Axis2 work with a older jar.
Thx for the suggestion! It's be great if you help out providing/testing
other WS stacks :)
Cheers,
-Kurt
Anil Saldhana wrote:
http://cxf.apache.org/ supports JAX-WS.
--- On *Mon, 12/1/08, Jeff Faath /<[EMAIL PROTECTED]>/* wrote:
From: Jeff Faath <[EMAIL PROTECTED]>
Subject: RE: jUDDI web services
To: [email protected], [EMAIL PROTECTED]
Date: Monday, December 1, 2008, 4:19 PM
No, it’s for the v3 release.
We are attempting to make the project WS-stack agnostic by using
JAX-WS. However, given this is an Apache project, we feel it is
important to get it to work with Axis2 and using that as the
default runtime.
*From:* Anil Saldhana [mailto:[EMAIL PROTECTED]
*Sent:* Monday, December 01, 2008 3:42 PM
*To:* [email protected]
*Subject:* Re: jUDDI web services
the JAX-WS enabled WS is for your testing? or juddi testsuite
will have it?
If it just for you to proceed, then why not just try to make it
JAX-WS and users will deploy it on their favorite runtime.
--- On *Fri, 11/28/08, Jeff Faath /<[EMAIL PROTECTED]>/* wrote:
From: Jeff Faath <[EMAIL PROTECTED]>
Subject: jUDDI web services
To: [email protected]
Date: Friday, November 28, 2008, 1:26 PM
All,
I was able to get further along in the investigation of getting
the JAX-WS web services to work with Tomcat and Axis2. Turns out
it wasn’t working before because Axis2 couldn’t properly deploy
the services when classes were compiled into a jar. I think there
is a way to configure Axis2 to deploy within a jar, but
unfortunately there is a bigger issue.
When trying to bring up the WSDL, I get a namespace conflict
issue. Upon further investigation, it turns out we are getting
hit by a flavor of WSCOMMONS-377. And this issue doesn’t look
like it’s going to get fixed anytime soon.
So, I’m not sure where to go from here. Any suggestions?
-JF
