[jira] Created: (FELIX-622) iPOJO Composite Service Instance can use factories twice to create service instance

iPOJO Composite Service Instance can use factories twice to create service instance
-----------------------------------------------------------------------------------

                 Key: FELIX-622
                 URL: https://issues.apache.org/jira/browse/FELIX-622
             Project: Felix
          Issue Type: Bug
          Components: iPOJO
    Affects Versions: iPOJO-0.8.0
            Reporter: Clement Escoffier
            Assignee: Clement Escoffier


When instantiating a service, an iPOJO composite can use a factory several time (for the same service). This must be avoid, as these instances are no disposed when the factory leaves or when the composite stops. This issue occurs when managing an aggregate & optional service instantiation.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/FELIX-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Clement Escoffier resolved FELIX-622.
-------------------------------------

    Resolution: Fixed

Issue fix by avoiding using twice the same factory to instantiate a service.

> iPOJO Composite Service Instance can use factories twice to create service instance
> -----------------------------------------------------------------------------------
>
>                 Key: FELIX-622
>                 URL: https://issues.apache.org/jira/browse/FELIX-622
>             Project: Felix
>          Issue Type: Bug
>          Components: iPOJO
>    Affects Versions: iPOJO-0.8.0
>            Reporter: Clement Escoffier
>            Assignee: Clement Escoffier
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> When instantiating a service, an iPOJO composite can use a factory several time (for the same service). This must be avoid, as these instances are no disposed when the factory leaves or when the composite stops. This issue occurs when managing an aggregate & optional service instantiation.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.