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/06/14 19:46:20 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=13683588#comment-13683588 ] 

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

Some work is done in : FELIX-4130.
https://issues.apache.org/jira/browse/FELIX-4130

ComponentInstance is now accessible from the instance description object. Instance descriptino are accessible from the Architecture service or from a managed object via the Pojo interface.
                
> 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