[
https://issues.apache.org/jira/browse/XMLBEANS-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492138
]
Radu Preotiuc-Pietro commented on XMLBEANS-324:
-----------------------------------------------
Yeah, and removing it in an XmlBeans release means that all the people who
don't have any problems right now and use JDK1.4 will now have their apps break
until the get the extra jar and add it to the classpath.
I think that the negatives far ouweigh the positives in this case and I would
vote for not making this change.
When everybody moves to JDK1.5 and later, the class will be loaded by the
bootstrap classloader and this will cease being a problem.
> Strange contents of JAR-files
> -----------------------------
>
> Key: XMLBEANS-324
> URL: https://issues.apache.org/jira/browse/XMLBEANS-324
> Project: XMLBeans
> Issue Type: Bug
> Affects Versions: Version 2.2
> Environment: All
> Reporter: Oskar Carlstedt
>
> Hello!!
> I have som deploying issues that are related to xml beans. Can someone tell
> me why javax.xml.namespae is included in xbean.jar and xmlpublic.jar. Also,
> why are these bundeled into xml beans. Isn't it better to leave them as a
> dependency to xml beans.
> Ok, I know that people hate dependencies to other jars - but anyway, today's
> solution makes me (and a lot of other people too) getting a
> java.lang.LinkedError when using the QName class.
> Is i tpossible to remove these classes ffrom the xml beans distribution.
> Best Regards
> Oskar Carlstedt
--
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]
