You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Freeman Fang (Created) (JIRA)" <ji...@apache.org> on 2011/12/24 07:32:30 UTC
[jira] [Created] (SMXCOMP-921) servicemix-camel blueprint
configuration use duplicated PID
servicemix-camel blueprint configuration use duplicated PID
-----------------------------------------------------------
Key: SMXCOMP-921
URL: https://issues.apache.org/jira/browse/SMXCOMP-921
Project: ServiceMix Components
Issue Type: Bug
Components: servicemix-camel
Reporter: Freeman Fang
it share same PID with servicemix-common bundle, which is against with the rule that
Do not share the same persistent-id (PID) between multiple bundles or definitions, as only one of them will receive notifications. managed-properties relies on org.osgi.service.cm.ManagedService contract which mandates that each ManagedService instance must be identified with its own unique PID. Please see the Configuration Admin spec, specifically section 104.3 and 104.5
We need change to use another PID
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (SMXCOMP-921) servicemix-camel blueprint
configuration use duplicated PID
Posted by "Freeman Fang (Work started) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SMXCOMP-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on SMXCOMP-921 started by Freeman Fang.
> servicemix-camel blueprint configuration use duplicated PID
> -----------------------------------------------------------
>
> Key: SMXCOMP-921
> URL: https://issues.apache.org/jira/browse/SMXCOMP-921
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-camel
> Reporter: Freeman Fang
> Assignee: Freeman Fang
>
> it share same PID with servicemix-common bundle, which is against with the rule that
> Do not share the same persistent-id (PID) between multiple bundles or definitions, as only one of them will receive notifications. managed-properties relies on org.osgi.service.cm.ManagedService contract which mandates that each ManagedService instance must be identified with its own unique PID. Please see the Configuration Admin spec, specifically section 104.3 and 104.5
> We need change to use another PID
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (SMXCOMP-921) servicemix-camel blueprint
configuration use duplicated PID
Posted by "Freeman Fang (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SMXCOMP-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang reassigned SMXCOMP-921:
------------------------------------
Assignee: Freeman Fang
> servicemix-camel blueprint configuration use duplicated PID
> -----------------------------------------------------------
>
> Key: SMXCOMP-921
> URL: https://issues.apache.org/jira/browse/SMXCOMP-921
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-camel
> Reporter: Freeman Fang
> Assignee: Freeman Fang
>
> it share same PID with servicemix-common bundle, which is against with the rule that
> Do not share the same persistent-id (PID) between multiple bundles or definitions, as only one of them will receive notifications. managed-properties relies on org.osgi.service.cm.ManagedService contract which mandates that each ManagedService instance must be identified with its own unique PID. Please see the Configuration Admin spec, specifically section 104.3 and 104.5
> We need change to use another PID
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SMXCOMP-921) servicemix-camel blueprint
configuration use duplicated PID
Posted by "Freeman Fang (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SMXCOMP-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved SMXCOMP-921.
----------------------------------
Resolution: Fixed
Fix Version/s: 2012.01
commit fix
http://svn.apache.org/viewvc?rev=1222918&view=rev
> servicemix-camel blueprint configuration use duplicated PID
> -----------------------------------------------------------
>
> Key: SMXCOMP-921
> URL: https://issues.apache.org/jira/browse/SMXCOMP-921
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-camel
> Reporter: Freeman Fang
> Assignee: Freeman Fang
> Fix For: 2012.01
>
>
> it share same PID with servicemix-common bundle, which is against with the rule that
> Do not share the same persistent-id (PID) between multiple bundles or definitions, as only one of them will receive notifications. managed-properties relies on org.osgi.service.cm.ManagedService contract which mandates that each ManagedService instance must be identified with its own unique PID. Please see the Configuration Admin spec, specifically section 104.3 and 104.5
> We need change to use another PID
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira