<ras>
*******************************************
Richard A. Sitze [EMAIL PROTECTED]
CORBA Interoperability & WebServices
IBM WebSphere Development
Jeremy Hughes/UK/IBM@IBMGB | 
06/26/2002 11:36 AM |  To: [EMAIL PROTECTED] cc: Matthew Duftler/Watson/IBM@IBMUS Subject: Re: Duplicate QName class |
The people on the JSR 110 call yesterday decided to move javax.xml.namespace.QName out into a separate jar ... see minutes posting yesterday. So when the WSDL4J build.xml has changed to reflect this, WSDL4J will build wsdl4j.jar (which won't contain QName) plus another small jar not dissimilar to Sun's jax-qname.jar
Axis can then build regularly and still pick up the QName from jaxrpc.jar. Anyone using WSDL4J without Axis will need the 'wsdl4j-jax-qname.jar' (or whatever it's going to be called)
Anyone running or building Axis will depend on wsdl4j.jar and jaxrpc.jar for the QName used by wsdl4j.jar. This should all work because javax.xml.namespace.QName has a standard interface :-)
This just needs a change to the WSDL4J build.xml file when the jars are being packaged.
Does this solve the problem or have I missed the point?
Kind regards,
Jeremy
------
I know there was some recent conversation related to this issue, and I think the concensus was NOT to use the Sun implementation because of licensing constraints. In the meantime, we still have java.xml.namespace.QName defined in two places (from AXISs' perspective):
jaxrpc.jar
wsdl4j.jar
We should remove it from one or the other. Given that AXIS pulls wsdl4j.jar, it doesn't make sense that wsdl4j introduce a dependency on AXIS::jaxrpc.jar (circular build dependency).
So:
1. Can we move jaxrpc.jar & source files into commons or some independent (small) project?
2. Alternatively, everyone OK with removing java.xml.namespace.QName from AXIS::jaxrpc.jar and depending upon the version in wsdl4j? Is the wsdl4j::QName up-to-par with the recent changes made to the AXIS version?
<ras>
*******************************************
Richard A. Sitze [EMAIL PROTECTED]
CORBA Interoperability & WebServices
IBM WebSphere Development
