felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Sauthier (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-3537) Make ComponentInstance more easily accessible
Date Tue, 05 Jun 2012 13:29:22 GMT

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

Guillaume Sauthier commented on FELIX-3537:

Another trick could be to let the ComponentInstance show off from the Architecture service
> 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
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message