[ http://issues.apache.org/jira/browse/WSCOMMONS-70?page=all ]
Jeremy Boynes updated WSCOMMONS-70:
-----------------------------------
Attachment: axiom.patch
This patch specifies the classloader to use and uses the classloader used to
load StAXUtils. In most applications this will be the same one originally
contained on the thread (for example, in a webapp where Axis is bundled in the
war).
Due to a defect in the stax-api library where
XMLOutputFactory.newInstace(String, ClassLoader) had the wrong return type, the
patch also upgrades to use version 1.0.1
> AXIOM does not specify the classloader used to locate StAX implementation
> -------------------------------------------------------------------------
>
> Key: WSCOMMONS-70
> URL: http://issues.apache.org/jira/browse/WSCOMMONS-70
> Project: WS-Commons
> Issue Type: Bug
> Components: AXIOM
> Reporter: Jeremy Boynes
> Attachments: axiom.patch
>
>
> The implementation in StAXUtils uses XMLInputFactory.newInstance() to load
> the pool which, with the stax-api version used, uses the current classloader
> to locate the StAX implementation. This has two problems:
> * it requires the implementation to be on the application's classpath
> * it may result in factories from different implementations being in the pool
> as different classloaders may be present when the factory is instantiated
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
