You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Paul Golick (JIRA)" <tu...@ws.apache.org> on 2006/05/02 20:06:46 UTC

[jira] Created: (TUSCANY-256) loadClass in SDOUtil receiving exception because different class loaders are used

loadClass in SDOUtil receiving exception because different class loaders are used
---------------------------------------------------------------------------------

         Key: TUSCANY-256
         URL: http://issues.apache.org/jira/browse/TUSCANY-256
     Project: Tuscany
        Type: Bug

  Components: Java SDO Implementation  
 Environment: all
    Reporter: Paul Golick


In SDOUtil.java it is necessary that the loadClass method be wrapped and done by invoking AccessController.doPriveleged on a PrivelegedExceptionAction object because the current class loader can be different than the one previously used to load the class.

-- 
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


[jira] Closed: (TUSCANY-256) loadClass in SDOUtil receiving exception because different class loaders are used

Posted by "Frank Budinsky (JIRA)" <tu...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/TUSCANY-256?page=all ]
     
Frank Budinsky closed TUSCANY-256:
----------------------------------


> loadClass in SDOUtil receiving exception because different class loaders are used
> ---------------------------------------------------------------------------------
>
>          Key: TUSCANY-256
>          URL: http://issues.apache.org/jira/browse/TUSCANY-256
>      Project: Tuscany
>         Type: Bug

>   Components: Java SDO Implementation
>  Environment: all
>     Reporter: Paul Golick
>  Attachments: patchSDOUtil.txt
>
> In SDOUtil.java it is necessary that the loadClass method be wrapped and done by invoking AccessController.doPriveleged on a PrivelegedExceptionAction object because the current class loader can be different than the one previously used to load the class.

-- 
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


[jira] Commented: (TUSCANY-256) loadClass in SDOUtil receiving exception because different class loaders are used

Posted by "Paul Golick (JIRA)" <tu...@ws.apache.org>.
    [ http://issues.apache.org/jira/browse/TUSCANY-256?page=comments#action_12377813 ] 

Paul Golick commented on TUSCANY-256:
-------------------------------------

Fix verified in revision 399056.  Please close this issue.

> loadClass in SDOUtil receiving exception because different class loaders are used
> ---------------------------------------------------------------------------------
>
>          Key: TUSCANY-256
>          URL: http://issues.apache.org/jira/browse/TUSCANY-256
>      Project: Tuscany
>         Type: Bug

>   Components: Java SDO Implementation
>  Environment: all
>     Reporter: Paul Golick
>  Attachments: patchSDOUtil.txt
>
> In SDOUtil.java it is necessary that the loadClass method be wrapped and done by invoking AccessController.doPriveleged on a PrivelegedExceptionAction object because the current class loader can be different than the one previously used to load the class.

-- 
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


[jira] Updated: (TUSCANY-256) loadClass in SDOUtil receiving exception because different class loaders are used

Posted by "Paul Golick (JIRA)" <tu...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/TUSCANY-256?page=all ]

Paul Golick updated TUSCANY-256:
--------------------------------

    Attachment: patchSDOUtil.txt

The attached patch file moves the loadClass method into a PrivelegedExceptionAction object and invokes it with a doPriveleged method.

> loadClass in SDOUtil receiving exception because different class loaders are used
> ---------------------------------------------------------------------------------
>
>          Key: TUSCANY-256
>          URL: http://issues.apache.org/jira/browse/TUSCANY-256
>      Project: Tuscany
>         Type: Bug

>   Components: Java SDO Implementation
>  Environment: all
>     Reporter: Paul Golick
>  Attachments: patchSDOUtil.txt
>
> In SDOUtil.java it is necessary that the loadClass method be wrapped and done by invoking AccessController.doPriveleged on a PrivelegedExceptionAction object because the current class loader can be different than the one previously used to load the class.

-- 
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


[jira] Resolved: (TUSCANY-256) loadClass in SDOUtil receiving exception because different class loaders are used

Posted by "Frank Budinsky (JIRA)" <tu...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/TUSCANY-256?page=all ]
     
Frank Budinsky resolved TUSCANY-256:
------------------------------------

    Resolution: Fixed

Fixed in revision 399033.

> loadClass in SDOUtil receiving exception because different class loaders are used
> ---------------------------------------------------------------------------------
>
>          Key: TUSCANY-256
>          URL: http://issues.apache.org/jira/browse/TUSCANY-256
>      Project: Tuscany
>         Type: Bug

>   Components: Java SDO Implementation
>  Environment: all
>     Reporter: Paul Golick
>  Attachments: patchSDOUtil.txt
>
> In SDOUtil.java it is necessary that the loadClass method be wrapped and done by invoking AccessController.doPriveleged on a PrivelegedExceptionAction object because the current class loader can be different than the one previously used to load the class.

-- 
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