[
https://issues.apache.org/jira/browse/XMLBEANS-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490243
]
Oskar Carlstedt commented on XMLBEANS-324:
------------------------------------------
Hello!
This happens i JBoss 4.0.x where I get a LinkedError when using isolated
classloaders on earfiles (i.e. server/default/deploy/ear-deployer.xml has the
value Isolated set to true). A better idea might be to not mix different things
in the same jar file. What I mean is, it is better to provide a new jar file
called javax-xml-namespace.jar with the javax.xml.namespace contents. Then it
is up to the user to use this jar file as a dedpendency or not.
I have removed the selected packages fom the jar file and that solved my
problem. But doing this way means that I have to patch my own xbean.jar
everytime you provide a new version.
Best
Oskar
> 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]
