Sharing of common utilitiy classes between extensions and extensions and
application breaks if classloader isolation is followed.
----------------------------------------------------------------------------------------------------------------------------------
Key: TUSCANY-871
URL: http://issues.apache.org/jira/browse/TUSCANY-871
Project: Tuscany
Issue Type: Bug
Reporter: Rick Rineholt
Priority: Critical
The current model tries to isolate each extension and the application to their
own classloader. This works ok until there is a need to share objects between
them. At this point these object's classs are each loaded by seperate
classloaders. Classes loaded this way don't work well. For example, a class
creating an instance by one classloader in an extension and then passed to an
application that has the same class loaded by another class loader will see a
classcast exception when an attempt is made to set a reference to the passed in
object.
Currently an example of this happens with databinding framework when using
SDOs. The application creates SDOs loaded by its classloader. When the SDO
object is sent on the wire the databinding framework intercepts to attempt to
convert SDO to axiom for a webservice interface. But SDO classes in the SDO
databinding framework are loaded via another classloader.
--
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]
