You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Clement Escoffier (JIRA)" <ji...@apache.org> on 2013/02/26 15:04:12 UTC

[jira] [Commented] (FELIX-3537) Make ComponentInstance more easily accessible

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

Clement Escoffier commented on FELIX-3537:
------------------------------------------

This will be fixed by the new MOP implemented for iPOJO 2.x.

The iPOJO MOP service will let you access all instances and factories.
                
> Make ComponentInstance more easily accessible
> ---------------------------------------------
>
>                 Key: FELIX-3537
>                 URL: https://issues.apache.org/jira/browse/FELIX-3537
>             Project: Felix
>          Issue Type: New Feature
>          Components: iPOJO
>            Reporter: Guillaume Sauthier
>            Assignee: Göktürk Gezer
>
> Currently, ComponentInstance works great with iPOJO's Factory:
> With the Factory, you can create a new ComponentInstance, and using the ComponentInstance returned, you have some control over the instance (start/stop/dispose/reconfigure).
> This is very nice, but the limitation is that the ComponentInstance is only known within your "session" with the Factory, you cannot access it outside.
> That means, for example, that an instance created from the metadata.xml will never be startable, stoppable or reconfigurable.
> So I would like to have a way to obtain ComponentInstance(s) from the iPOJO API.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira