[
https://issues.apache.org/jira/browse/WODEN-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534134
]
Jeremy Hughes commented on WODEN-182:
-------------------------------------
+1 to splitting the QName class out of woden.jar ... I hadn't realised it was
in there, but when I think about it, of course it's there. Splitting out QName
into a jar of its own is exactly what we did with WSDL4J. Ideally we would
remove QName, but QName isn't in Java 1.4.2 so it's needed there.
> Private QName class causes classloading issues
> ----------------------------------------------
>
> Key: WODEN-182
> URL: https://issues.apache.org/jira/browse/WODEN-182
> Project: Woden
> Issue Type: Bug
> Components: Parser
> Affects Versions: M7b
> Reporter: Lawrence Mandel
> Assignee: John Kaputin
> Attachments: qnamebuild.patch
>
>
> I'm using Woden in an OSGi environment with the Sun Java 5 SDK. In this case
> the SDK contains a version of QName in the same package as that used
> privately be Woden.
> The duplicate QName class causes classloading issues as certain OSGi bundles
> have access to QName from the SDK and certain bundles have access to QName
> from Woden. (This is due to the classloading nature of OSGi.) I think it's
> best if Woden remove this private version of QName. If it is required for
> older Java runtimes and is not available from another source we can create a
> separate QName jar that can be optionally added for older runtimes and does
> not need to be present for Java 5 and later runtimes.
--
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]
