[
https://issues.apache.org/jira/browse/XMLBEANS-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494352
]
David J. M. Karlsen commented on XMLBEANS-330:
----------------------------------------------
Yeah, I've removed the classes to verify the solution - but I still think it's
a *very bad* solution.
There are 3 points to be made on this issue:
1)
The classes (or interfaces) are part of an API specification because they're
supposed to be interoperable - and in fact an API! They are downloadable at
java.sun.com and dev.java.net. We simply can't just stuff in "things" because
it's handy - that's why there are specs for both APIs and JDKs. They are even
available at: http://repo1.maven.org/maven2/xml-apis/xml-apis/ - so xmlbeans
should instead depend on the appropiate xml-apis version. This separates
implementations from specifications - which is a really good idea.
2)
If such hacks should be done, package variants with suitable maven2
<classifier> tags - so clean versions are downloadable, and "handy" jars
suitable for JDK1.3 / 1.4 are available.
3)
This essientially breaks the maven-idea, so all users have to download the
original archives, remove extra classes, repackage them, and place them under
their repos under different names. This again will lead to a lot of <exclude>
and addition of "manual dependencies" (in our case we used axis2's xmlbeans
mapping, which depends on the spoken of xmlbeans archive). This again will
probably lead to less popularity of maven2 - especially in large enterprises
(which could afford to contribute to maven2) - which is really sad.
I strongly encourage the xmlbeans project to change it's practice.
That said, thanks for the project... :-)
> javax.xml.namespace classes included in archive
> -----------------------------------------------
>
> Key: XMLBEANS-330
> URL: https://issues.apache.org/jira/browse/XMLBEANS-330
> Project: XMLBeans
> Issue Type: Bug
> Affects Versions: Version 2.2
> Environment: N/A
> Reporter: David J. M. Karlsen
> Assigned To: Jacob Danner
> Priority: Blocker
>
> The archive at http://repo1.maven.org/maven2/xmlbeans/xbean/2.2.0/ includes
> javax.xml.namespace classes (QName and NamespaceContext) - which are part of
> the API specification - and thus should not be included in the archive.
> This is especially problematic when using xbeans inside containers which also
> loads these classes, ending up in ClassCast exceptions, LinkageError and the
> likes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
