[
https://issues.apache.org/jira/browse/FELIX-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295934#comment-13295934
]
Fabio Lattario Fonseca edited comment on FELIX-3537 at 6/15/12 9:27 PM:
------------------------------------------------------------------------
Also, I think the notification system you have envisioned could be done thought
callbacks to the Architecture[] field. With something like these one could have
a parallel control of the instances, disposing, reconfiguring and creating new
ones. It would be great for my work here.
Regards,
Fabio
was (Author: fabiolf):
Also, I think the notification system you have envisioned could be done
thought callbacks to the Architecture[] field.
> 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
