[
https://issues.apache.org/jira/browse/TUSCANY-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105986#comment-13105986
]
Simon Laws commented on TUSCANY-3946:
-------------------------------------
I have a local change that, before setting and resetting TCCL in
JavaImplementationInvoker, asks whether the TCCL is already set to the
contribution classloader. This is a simple change that requires no
configuration and which shouldn't upset anything else.
However I note that this change makes the same assumption that you're debating
in TUSCANY-3947 so we need to work out what the answer to that is before
closing this JIRA. I'll still commit my change for this assuming I get a clean
build.
> Capability to skip setting TCCL in JavaImplementationInvoker.invoke()
> ---------------------------------------------------------------------
>
> Key: TUSCANY-3946
> URL: https://issues.apache.org/jira/browse/TUSCANY-3946
> Project: Tuscany
> Issue Type: Improvement
> Components: SCA Java Runtime
> Affects Versions: Java-SCA-2.x
> Reporter: Jennifer A Thompson
> Assignee: Simon Laws
> Fix For: Java-SCA-2.x
>
>
> Setting the TCCL in the JavaImplementationInvoker can interfere with runtimes
> extending the Tuscany OASIS runtime. So there should be a mechanism for
> products extending the runtime to be able to skip setting the TCCL in
> JavaImplementationInvoker.invoke().
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
