You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Emily Jiang (JIRA)" <ji...@apache.org> on 2010/10/07 22:13:30 UTC
[jira] Created: (ARIES-444) Register the default local platform
service in a separate bundle rather than in the appliation utils
Register the default local platform service in a separate bundle rather than in the appliation utils
----------------------------------------------------------------------------------------------------
Key: ARIES-444
URL: https://issues.apache.org/jira/browse/ARIES-444
Project: Aries
Issue Type: Bug
Components: Application
Reporter: Emily Jiang
Attachments: jira-444.diff
There are two issues this jira is trying to address:
1. The default local platform service cannot be excluded when an application server consumes the application bundles.
At the moment, the default local platform service is registered by the bundle of application utils. An application server normally wishes to supply their own platform service. If we don't separate this service from the application utils bundle, the default service will make its way to an application server's service registry. It will be wired to Aries Application manager bundle before the good dedicated local platform service becomes available. This will cause unpredictable behaviour.
2. In application itests, we need to get rid of the hack, blocking one bundle from starting until another bundle has started, because a real fix has been delivered for the the problem of the hack tring to solve.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ARIES-444) Register the default local platform
service in a separate bundle rather than in the appliation utils
Posted by "Emily Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emily Jiang updated ARIES-444:
------------------------------
Attachment: jira-444.diff
This patch was generated from trunk dir.
> Register the default local platform service in a separate bundle rather than in the appliation utils
> ----------------------------------------------------------------------------------------------------
>
> Key: ARIES-444
> URL: https://issues.apache.org/jira/browse/ARIES-444
> Project: Aries
> Issue Type: Bug
> Components: Application
> Reporter: Emily Jiang
> Assignee: Emily Jiang
> Attachments: jira-444.diff
>
>
> There are two issues this jira is trying to address:
> 1. The default local platform service cannot be excluded when an application server consumes the application bundles.
> At the moment, the default local platform service is registered by the bundle of application utils. An application server normally wishes to supply their own platform service. If we don't separate this service from the application utils bundle, the default service will make its way to an application server's service registry. It will be wired to Aries Application manager bundle before the good dedicated local platform service becomes available. This will cause unpredictable behaviour.
> 2. In application itests, we need to get rid of the hack, blocking one bundle from starting until another bundle has started, because a real fix has been delivered for the the problem of the hack tring to solve.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ARIES-444) Register the default local platform
service in a separate bundle rather than in the appliation utils
Posted by "Mark Nuttall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Nuttall resolved ARIES-444.
--------------------------------
Resolution: Fixed
Resolved.
> Register the default local platform service in a separate bundle rather than in the appliation utils
> ----------------------------------------------------------------------------------------------------
>
> Key: ARIES-444
> URL: https://issues.apache.org/jira/browse/ARIES-444
> Project: Aries
> Issue Type: Bug
> Components: Application
> Reporter: Emily Jiang
> Assignee: Emily Jiang
> Attachments: jira-444.diff
>
>
> There are two issues this jira is trying to address:
> 1. The default local platform service cannot be excluded when an application server consumes the application bundles.
> At the moment, the default local platform service is registered by the bundle of application utils. An application server normally wishes to supply their own platform service. If we don't separate this service from the application utils bundle, the default service will make its way to an application server's service registry. It will be wired to Aries Application manager bundle before the good dedicated local platform service becomes available. This will cause unpredictable behaviour.
> 2. In application itests, we need to get rid of the hack, blocking one bundle from starting until another bundle has started, because a real fix has been delivered for the the problem of the hack tring to solve.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ARIES-444) Register the default local platform
service in a separate bundle rather than in the appliation utils
Posted by "Emily Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emily Jiang reassigned ARIES-444:
---------------------------------
Assignee: Emily Jiang
> Register the default local platform service in a separate bundle rather than in the appliation utils
> ----------------------------------------------------------------------------------------------------
>
> Key: ARIES-444
> URL: https://issues.apache.org/jira/browse/ARIES-444
> Project: Aries
> Issue Type: Bug
> Components: Application
> Reporter: Emily Jiang
> Assignee: Emily Jiang
> Attachments: jira-444.diff
>
>
> There are two issues this jira is trying to address:
> 1. The default local platform service cannot be excluded when an application server consumes the application bundles.
> At the moment, the default local platform service is registered by the bundle of application utils. An application server normally wishes to supply their own platform service. If we don't separate this service from the application utils bundle, the default service will make its way to an application server's service registry. It will be wired to Aries Application manager bundle before the good dedicated local platform service becomes available. This will cause unpredictable behaviour.
> 2. In application itests, we need to get rid of the hack, blocking one bundle from starting until another bundle has started, because a real fix has been delivered for the the problem of the hack tring to solve.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.