On Sep 22, 2006, at 11:00 AM, Eran Chinthaka wrote:

Jeremy Boynes wrote:
On Sep 21, 2006, at 5:38 AM, Jeremy Hughes wrote:


It needs NamespaceContext as well so that one won't work.

I didn't see that. Thanks.


We can still use stax-api, but how about scoping it to provided/ optional
so that it is not pulled in as a transitive dependency.

No since QName is so common and used everywhere.

That's kind of why we don't want to pull it in - by doing so we increase the potential for conflict with other things (which is what we have now in the form of a conflict with axiom/axis2). This is even worse in that we are pulling in an API (stax) that we are not actually using.

The downside
will mean the user needs to provide a version of javax.xml.namespace,
but that is already part of both J2EE1.4 and Java5

Remember our minimum requirement is JDK 1.4 nothing else and it doesn't
contain QName, IIRC.

Right and we need to support that. However, by hard-coding a dependency here we are introducing a direct conflict with two very common environments. IMO, better to say that in basic 1.4 environments the user should supply their own version of javax.xml.namespace (which is what they need to do outside a Maven2 environment anyway) rather than forcing stax on them.

So basically, the only thing we are not supporting is users who use Maven2 on JDK1.4 and who want to use a transitive dependency from XmlSchema to get javax.xml.namespace onto the classpath. The upside is we avoid conflicts for all other users.

--
Jeremy


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to