You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Rajini Sivaram (JIRA)" <tu...@ws.apache.org> on 2007/11/01 14:43:50 UTC

[jira] Created: (TUSCANY-1887) Classloading: Remove unnecessary use of thread context classloader

Classloading: Remove unnecessary use of thread context classloader
------------------------------------------------------------------

                 Key: TUSCANY-1887
                 URL: https://issues.apache.org/jira/browse/TUSCANY-1887
             Project: Tuscany
          Issue Type: Improvement
          Components: Java SCA Core Runtime
            Reporter: Rajini Sivaram


The attached patch removes some of the uses of TCCL in Tuscany code.

ModelResolver (and hence the contribution classloader) is now used to resolve:
    Property file specified as component property, if the filename specified is relative
    Script file specified for <implementation.script>
    Xquery file specified for <implementation.xquery/>

There are some uses of TCCL in testing, which have been left as is.
TCCL will continue to be used as the parent classloader for all classloaders created within Tuscany.

<implementation.spring/> and <binding.ejb/> still use TCCL. I didn't want to remove the use of TCCL in this code because I wasn't sure if Spring and EJB have additional requirements on TCCL which are not obvious from the Tuscany code.

I will raise another JIRA issue to handle deserializing of CallableReference, which currently uses TCCL.


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


[jira] Assigned: (TUSCANY-1887) Classloading: Remove unnecessary use of thread context classloader

Posted by "Venkatakrishnan (JIRA)" <tu...@ws.apache.org>.
     [ https://issues.apache.org/jira/browse/TUSCANY-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Venkatakrishnan reassigned TUSCANY-1887:
----------------------------------------

    Assignee: Venkatakrishnan

> Classloading: Remove unnecessary use of thread context classloader
> ------------------------------------------------------------------
>
>                 Key: TUSCANY-1887
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1887
>             Project: Tuscany
>          Issue Type: Improvement
>          Components: Java SCA Core Runtime
>            Reporter: Rajini Sivaram
>            Assignee: Venkatakrishnan
>         Attachments: new-tuscany-tccl-patch.txt
>
>
> The attached patch removes some of the uses of TCCL in Tuscany code.
> ModelResolver (and hence the contribution classloader) is now used to resolve:
>     Property file specified as component property, if the filename specified is relative
>     Script file specified for <implementation.script>
>     Xquery file specified for <implementation.xquery/>
> There are some uses of TCCL in testing, which have been left as is.
> TCCL will continue to be used as the parent classloader for all classloaders created within Tuscany.
> <implementation.spring/> and <binding.ejb/> still use TCCL. I didn't want to remove the use of TCCL in this code because I wasn't sure if Spring and EJB have additional requirements on TCCL which are not obvious from the Tuscany code.
> I will raise another JIRA issue to handle deserializing of CallableReference, which currently uses TCCL.

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


[jira] Updated: (TUSCANY-1887) Classloading: Remove unnecessary use of thread context classloader

Posted by "Rajini Sivaram (JIRA)" <tu...@ws.apache.org>.
     [ https://issues.apache.org/jira/browse/TUSCANY-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajini Sivaram updated TUSCANY-1887:
------------------------------------

    Attachment: tuscany-tccl-patch.txt

This patch also contains the changes from 1877 (https://issues.apache.org/jira/browse/TUSCANY-1877), since there are dependencies.

> Classloading: Remove unnecessary use of thread context classloader
> ------------------------------------------------------------------
>
>                 Key: TUSCANY-1887
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1887
>             Project: Tuscany
>          Issue Type: Improvement
>          Components: Java SCA Core Runtime
>            Reporter: Rajini Sivaram
>         Attachments: tuscany-tccl-patch.txt
>
>
> The attached patch removes some of the uses of TCCL in Tuscany code.
> ModelResolver (and hence the contribution classloader) is now used to resolve:
>     Property file specified as component property, if the filename specified is relative
>     Script file specified for <implementation.script>
>     Xquery file specified for <implementation.xquery/>
> There are some uses of TCCL in testing, which have been left as is.
> TCCL will continue to be used as the parent classloader for all classloaders created within Tuscany.
> <implementation.spring/> and <binding.ejb/> still use TCCL. I didn't want to remove the use of TCCL in this code because I wasn't sure if Spring and EJB have additional requirements on TCCL which are not obvious from the Tuscany code.
> I will raise another JIRA issue to handle deserializing of CallableReference, which currently uses TCCL.

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


[jira] Commented: (TUSCANY-1887) Classloading: Remove unnecessary use of thread context classloader

Posted by "Rajini Sivaram (JIRA)" <tu...@ws.apache.org>.
    [ https://issues.apache.org/jira/browse/TUSCANY-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539559 ] 

Rajini Sivaram commented on TUSCANY-1887:
-----------------------------------------

Venkat,

Thank you for integrating https://issues.apache.org/jira/browse/TUSCANY-1877. I will provide a new patch for this one.

- Rajini


> Classloading: Remove unnecessary use of thread context classloader
> ------------------------------------------------------------------
>
>                 Key: TUSCANY-1887
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1887
>             Project: Tuscany
>          Issue Type: Improvement
>          Components: Java SCA Core Runtime
>            Reporter: Rajini Sivaram
>         Attachments: tuscany-tccl-patch.txt
>
>
> The attached patch removes some of the uses of TCCL in Tuscany code.
> ModelResolver (and hence the contribution classloader) is now used to resolve:
>     Property file specified as component property, if the filename specified is relative
>     Script file specified for <implementation.script>
>     Xquery file specified for <implementation.xquery/>
> There are some uses of TCCL in testing, which have been left as is.
> TCCL will continue to be used as the parent classloader for all classloaders created within Tuscany.
> <implementation.spring/> and <binding.ejb/> still use TCCL. I didn't want to remove the use of TCCL in this code because I wasn't sure if Spring and EJB have additional requirements on TCCL which are not obvious from the Tuscany code.
> I will raise another JIRA issue to handle deserializing of CallableReference, which currently uses TCCL.

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


[jira] Commented: (TUSCANY-1887) Classloading: Remove unnecessary use of thread context classloader

Posted by "Venkatakrishnan (JIRA)" <tu...@ws.apache.org>.
    [ https://issues.apache.org/jira/browse/TUSCANY-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539519 ] 

Venkatakrishnan commented on TUSCANY-1887:
------------------------------------------

I've committed the patch for https://issues.apache.org/jira/browse/TUSCANY-1877 not realizing that this is a cummulative one.  Any chance of including a patch just for this JIRA after updating from the Trunk (which now has all that you need as part of 1877).   Thanks.

> Classloading: Remove unnecessary use of thread context classloader
> ------------------------------------------------------------------
>
>                 Key: TUSCANY-1887
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1887
>             Project: Tuscany
>          Issue Type: Improvement
>          Components: Java SCA Core Runtime
>            Reporter: Rajini Sivaram
>         Attachments: tuscany-tccl-patch.txt
>
>
> The attached patch removes some of the uses of TCCL in Tuscany code.
> ModelResolver (and hence the contribution classloader) is now used to resolve:
>     Property file specified as component property, if the filename specified is relative
>     Script file specified for <implementation.script>
>     Xquery file specified for <implementation.xquery/>
> There are some uses of TCCL in testing, which have been left as is.
> TCCL will continue to be used as the parent classloader for all classloaders created within Tuscany.
> <implementation.spring/> and <binding.ejb/> still use TCCL. I didn't want to remove the use of TCCL in this code because I wasn't sure if Spring and EJB have additional requirements on TCCL which are not obvious from the Tuscany code.
> I will raise another JIRA issue to handle deserializing of CallableReference, which currently uses TCCL.

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


[jira] Updated: (TUSCANY-1887) Classloading: Remove unnecessary use of thread context classloader

Posted by "Rajini Sivaram (JIRA)" <tu...@ws.apache.org>.
     [ https://issues.apache.org/jira/browse/TUSCANY-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajini Sivaram updated TUSCANY-1887:
------------------------------------

    Attachment:     (was: tuscany-tccl-patch.txt)

> Classloading: Remove unnecessary use of thread context classloader
> ------------------------------------------------------------------
>
>                 Key: TUSCANY-1887
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1887
>             Project: Tuscany
>          Issue Type: Improvement
>          Components: Java SCA Core Runtime
>            Reporter: Rajini Sivaram
>         Attachments: new-tuscany-tccl-patch.txt
>
>
> The attached patch removes some of the uses of TCCL in Tuscany code.
> ModelResolver (and hence the contribution classloader) is now used to resolve:
>     Property file specified as component property, if the filename specified is relative
>     Script file specified for <implementation.script>
>     Xquery file specified for <implementation.xquery/>
> There are some uses of TCCL in testing, which have been left as is.
> TCCL will continue to be used as the parent classloader for all classloaders created within Tuscany.
> <implementation.spring/> and <binding.ejb/> still use TCCL. I didn't want to remove the use of TCCL in this code because I wasn't sure if Spring and EJB have additional requirements on TCCL which are not obvious from the Tuscany code.
> I will raise another JIRA issue to handle deserializing of CallableReference, which currently uses TCCL.

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


[jira] Resolved: (TUSCANY-1887) Classloading: Remove unnecessary use of thread context classloader

Posted by "Venkatakrishnan (JIRA)" <tu...@ws.apache.org>.
     [ https://issues.apache.org/jira/browse/TUSCANY-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Venkatakrishnan resolved TUSCANY-1887.
--------------------------------------

    Resolution: Fixed

Thanks for the patch.  I appreciate your re-doing the patch just for this delta.  Applied under r591560.

> Classloading: Remove unnecessary use of thread context classloader
> ------------------------------------------------------------------
>
>                 Key: TUSCANY-1887
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1887
>             Project: Tuscany
>          Issue Type: Improvement
>          Components: Java SCA Core Runtime
>            Reporter: Rajini Sivaram
>            Assignee: Venkatakrishnan
>         Attachments: new-tuscany-tccl-patch.txt
>
>
> The attached patch removes some of the uses of TCCL in Tuscany code.
> ModelResolver (and hence the contribution classloader) is now used to resolve:
>     Property file specified as component property, if the filename specified is relative
>     Script file specified for <implementation.script>
>     Xquery file specified for <implementation.xquery/>
> There are some uses of TCCL in testing, which have been left as is.
> TCCL will continue to be used as the parent classloader for all classloaders created within Tuscany.
> <implementation.spring/> and <binding.ejb/> still use TCCL. I didn't want to remove the use of TCCL in this code because I wasn't sure if Spring and EJB have additional requirements on TCCL which are not obvious from the Tuscany code.
> I will raise another JIRA issue to handle deserializing of CallableReference, which currently uses TCCL.

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


[jira] Updated: (TUSCANY-1887) Classloading: Remove unnecessary use of thread context classloader

Posted by "Rajini Sivaram (JIRA)" <tu...@ws.apache.org>.
     [ https://issues.apache.org/jira/browse/TUSCANY-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajini Sivaram updated TUSCANY-1887:
------------------------------------

    Attachment: new-tuscany-tccl-patch.txt

New patch generated after the integration of  TUSCANY-1877.

> Classloading: Remove unnecessary use of thread context classloader
> ------------------------------------------------------------------
>
>                 Key: TUSCANY-1887
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1887
>             Project: Tuscany
>          Issue Type: Improvement
>          Components: Java SCA Core Runtime
>            Reporter: Rajini Sivaram
>         Attachments: new-tuscany-tccl-patch.txt
>
>
> The attached patch removes some of the uses of TCCL in Tuscany code.
> ModelResolver (and hence the contribution classloader) is now used to resolve:
>     Property file specified as component property, if the filename specified is relative
>     Script file specified for <implementation.script>
>     Xquery file specified for <implementation.xquery/>
> There are some uses of TCCL in testing, which have been left as is.
> TCCL will continue to be used as the parent classloader for all classloaders created within Tuscany.
> <implementation.spring/> and <binding.ejb/> still use TCCL. I didn't want to remove the use of TCCL in this code because I wasn't sure if Spring and EJB have additional requirements on TCCL which are not obvious from the Tuscany code.
> I will raise another JIRA issue to handle deserializing of CallableReference, which currently uses TCCL.

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