You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Joe Bohn (JIRA)" <ji...@apache.org> on 2010/07/22 05:12:49 UTC
[jira] Created: (ARIES-368) Samples should lookup osgi services
spec compliant using "osgi:service" rather than "aries:services" unless
specific aries:service capabilities are needed
Samples should lookup osgi services spec compliant using "osgi:service" rather than "aries:services" unless specific aries:service capabilities are needed
----------------------------------------------------------------------------------------------------------------------------------------------------------
Key: ARIES-368
URL: https://issues.apache.org/jira/browse/ARIES-368
Project: Aries
Issue Type: Improvement
Components: Samples
Affects Versions: 0.1
Reporter: Joe Bohn
Assignee: Joe Bohn
Fix For: 0.2
Currently the samples use a jndi prefix of "aries:services" rather than the spec compliant "osgi:service". Up until now the results of these 2 calls has been the same. However, changes are being implemented to make them different. Unless there is a specific need for aries specific capabilities our samples should use the osgi:service prefix.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (ARIES-368) Samples should lookup osgi
services spec compliant using "osgi:service" rather than "aries:services"
unless specific aries:service capabilities are needed
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on ARIES-368 started by Joe Bohn.
> Samples should lookup osgi services spec compliant using "osgi:service" rather than "aries:services" unless specific aries:service capabilities are needed
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ARIES-368
> URL: https://issues.apache.org/jira/browse/ARIES-368
> Project: Aries
> Issue Type: Improvement
> Components: Samples
> Affects Versions: 0.1
> Reporter: Joe Bohn
> Assignee: Joe Bohn
> Fix For: 0.2
>
>
> Currently the samples use a jndi prefix of "aries:services" rather than the spec compliant "osgi:service". Up until now the results of these 2 calls has been the same. However, changes are being implemented to make them different. Unless there is a specific need for aries specific capabilities our samples should use the osgi:service prefix.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ARIES-368) Samples should lookup osgi services
spec compliant using "osgi:service" rather than "aries:services" unless
specific aries:service capabilities are needed
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bohn resolved ARIES-368.
----------------------------
Resolution: Fixed
> Samples should lookup osgi services spec compliant using "osgi:service" rather than "aries:services" unless specific aries:service capabilities are needed
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ARIES-368
> URL: https://issues.apache.org/jira/browse/ARIES-368
> Project: Aries
> Issue Type: Improvement
> Components: Samples
> Affects Versions: 0.1
> Reporter: Joe Bohn
> Assignee: Joe Bohn
> Fix For: 0.2
>
>
> Currently the samples use a jndi prefix of "aries:services" rather than the spec compliant "osgi:service". Up until now the results of these 2 calls has been the same. However, changes are being implemented to make them different. Unless there is a specific need for aries specific capabilities our samples should use the osgi:service prefix.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (ARIES-368) Samples should lookup osgi services spec
compliant using "osgi:service" rather than "aries:services" unless specific
aries:service capabilities are needed
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bohn closed ARIES-368.
--------------------------
> Samples should lookup osgi services spec compliant using "osgi:service" rather than "aries:services" unless specific aries:service capabilities are needed
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ARIES-368
> URL: https://issues.apache.org/jira/browse/ARIES-368
> Project: Aries
> Issue Type: Improvement
> Components: Samples
> Affects Versions: 0.1
> Reporter: Joe Bohn
> Assignee: Joe Bohn
> Fix For: 0.2
>
>
> Currently the samples use a jndi prefix of "aries:services" rather than the spec compliant "osgi:service". Up until now the results of these 2 calls has been the same. However, changes are being implemented to make them different. Unless there is a specific need for aries specific capabilities our samples should use the osgi:service prefix.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.