OMAbstractFactory should use thread context classloader rather than
Class.forName(omFactory)
--------------------------------------------------------------------------------------------
Key: WSCOMMONS-271
URL: https://issues.apache.org/jira/browse/WSCOMMONS-271
Project: WS-Commons
Issue Type: Improvement
Components: AXIOM
Reporter: Todd Wolff
Different 'deployments' should be able to 'share' the axiom api artifact, i.e.
deployments should be able to hide their choice of implementation from other
'deployments.' By using Class.forName(), which uses OMAbstractFactory's
defining classloader, and requiring a system property to identify the factory
impl, the choice of implementation must be the same for all 'deployments.'
If thread context classloader is used instead, along with the java service
provider loading mechanism, each deployment could effectively 'scope' its
desired version of the axiom impl artifact to its deployment (each of which has
its own classloader), along with a service provider file which indicates the
factory impl choice. The axiom api artifact (loaded by a 'shared' classloader)
could then be 'shared' across deployments.
--
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]
