You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Jim Marino (JIRA)" <tu...@ws.apache.org> on 2007/03/04 08:37:51 UTC

[jira] Updated: (TUSCANY-871) Sharing of common utilitiy classes between extensions and extensions and application breaks if classloader isolation is followed.

     [ https://issues.apache.org/jira/browse/TUSCANY-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Marino updated TUSCANY-871:
-------------------------------

        Fix Version/s:     (was: Java-SCA-M3)
                       Java-SCA-2.0-Alpha
    Affects Version/s:     (was: Java-SCA-M3)
                       Java-SCA-2.0-Alpha

> Sharing of  common utilitiy classes between extensions and extensions and application breaks if classloader isolation is followed.
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-871
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-871
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Core
>    Affects Versions: Java-SCA-2.0-Alpha
>            Reporter: Rick Rineholt
>         Assigned To: Raymond Feng
>            Priority: Critical
>             Fix For: Java-SCA-2.0-Alpha
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org