[WODEN-182] Private QName class causes classloading issues

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: M7b
• Fix Version/s: M9
• Component/s: Parser
• Assignee: John Alan William Kaputin
• Reporter: Lawrence Mandel
• Created: 10/Oct/07 19:13
• Updated: 16/Sep/09 15:43
• Resolved: 14/Sep/09 15:47

Description

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.

Issue Links

• relates to: WODEN-57 Use ws-commons-java5 for QName class