You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Marcel Hanser (JIRA)" <ji...@apache.org> on 2012/06/27 12:52:45 UTC

[jira] [Commented] (ARIES-584) Blueprint Managed Service Factory Instantiates Duplicate Service

    [ https://issues.apache.org/jira/browse/ARIES-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402133#comment-13402133 ] 

Marcel Hanser commented on ARIES-584:
-------------------------------------

Currently the {{org.apache.aries.blueprint.compendium.cm.CmManagedServiceFactory}} lists the CM configurations and calls the {{updated}} method manually in the {{init}} method. But the method is called a second time by the configuration admin after service registration as specified. See attached patch to avoid the first {{updated}} call in the {{init}} method. I would also remove the mutex object which is locked during service registration but I am a little bit unsure to remove locks from code i didn't write ;) The patch works fine on our container (Felix 4.0.2, Blueprint 0.3.1, ConfigurationAdmin 1.2.8). I added two patches one for blueprint-cm 0.3.1 and for the current trunk.
                
> Blueprint Managed Service Factory Instantiates Duplicate Service
> ----------------------------------------------------------------
>
>                 Key: ARIES-584
>                 URL: https://issues.apache.org/jira/browse/ARIES-584
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>    Affects Versions: 0.2, 0.3
>         Environment: Mac OSX 10.6.6 / Equinox 3.6.1 / Felix Config Admin 1.2.8 / Aries Blueprint 0.3 (and 0.2)
>            Reporter: Greg Rapp
>         Attachments: logs.txt, org.apache.aries.blueprint.cm-0.3.1.patch, org.apache.aries.blueprint.cm.patch-withtrunk.patch
>
>
> Creating a simple managed service factory, two services are instantiated for a single factory configuration.

--
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