Can we use an older version of this jar? Before they broke it?
Jeff Faath wrote:
The jar file is not the problem. WSCOMMONS-377 is. We'll be hit by that
bug no matter how the classes are deployed.
-----Original Message-----
From: Tom Cunningham [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 29, 2008 4:23 PM
To: [email protected]
Subject: Re: jUDDI web services
If we uncompress the juddi-core service classes into WEB-INF/classes,
will that work?
Jeff Faath wrote:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
