You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Laws (JIRA)" <de...@tuscany.apache.org> on 2010/01/14 10:14:56 UTC
[jira] Created: (TUSCANY-3424) SCAClientFactory pluggability -
correct the behaviour of SCAClientFactory when running in OSGi or mixed
OSGi/JSE environments
SCAClientFactory pluggability - correct the behaviour of SCAClientFactory when running in OSGi or mixed OSGi/JSE environments
-----------------------------------------------------------------------------------------------------------------------------
Key: TUSCANY-3424
URL: https://issues.apache.org/jira/browse/TUSCANY-3424
Project: Tuscany
Issue Type: Improvement
Components: Java SCA Core Runtime
Affects Versions: Java-SCA-2.0-M4
Environment: All
Reporter: Simon Laws
Fix For: Java-SCA-2.0
The OASIS JCAA spec defined the mechanisms by which the SCAClientFactory implementation can be found. Our code, as it stands, works well in the JSE environment and relies on the SCAClientFactoryFinder as provided by OASIS. This doesn't work in the OSGi or mixed JSE/OSGi case. We need to revert to the default factory injection approach that is supported. There are a number of issues with this.
The OASIS defaultFactory injection approach doesn't take account of the possibility of multiple domains. The factory finder approach does. Needs raising with OASIS.
The Tuscany code doesn't currently do any injection so this needs to be added.
There is potentially an issue with the factory finder in terms of the order in which it established which classloader to use. Needs further invetigation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-3424) SCAClientFactory pluggability -
correct the behaviour of SCAClientFactory when running in OSGi or mixed
OSGi/JSE environments
Posted by "Simon Laws (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Laws resolved TUSCANY-3424.
---------------------------------
Resolution: Fixed
OASIS updated the client API so that the factory finder is injected instead of a default factory instance. Hence the pluggable factory finder can take responsibility for creating domain specific factory instances.
> SCAClientFactory pluggability - correct the behaviour of SCAClientFactory when running in OSGi or mixed OSGi/JSE environments
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3424
> URL: https://issues.apache.org/jira/browse/TUSCANY-3424
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-2.0-M4
> Environment: All
> Reporter: Simon Laws
> Fix For: Java-SCA-2.0
>
>
> The OASIS JCAA spec defined the mechanisms by which the SCAClientFactory implementation can be found. Our code, as it stands, works well in the JSE environment and relies on the SCAClientFactoryFinder as provided by OASIS. This doesn't work in the OSGi or mixed JSE/OSGi case. We need to revert to the default factory injection approach that is supported. There are a number of issues with this.
> The OASIS defaultFactory injection approach doesn't take account of the possibility of multiple domains. The factory finder approach does. Needs raising with OASIS.
> The Tuscany code doesn't currently do any injection so this needs to be added.
> There is potentially an issue with the factory finder in terms of the order in which it established which classloader to use. Needs further invetigation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.