[
https://issues.apache.org/jira/browse/FELIX-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13393547#comment-13393547
]
Göktürk Gezer edited comment on FELIX-3537 at 6/17/12 2:21 PM:
---------------------------------------------------------------
Hi,
Architecture exposition must be left as it is without putting extra mechanisms
into it to expose ComponentInstance, because that is so much for Architecture's
purpose IMO. But some way to access ComponentInstance and also its lifecycle
events would be clearly an improvement. Factory is surely a place to implement
such mechanism with filtering facility.
And i also think ComponentInstance service-object should be registered as OSGI
service for every component created like DeclerativeService does. So client can
either use Factory's facilities or directly access ComponentInstance itself.
But that approach needs a little discussion IMO.
I'll look into this issue as soon as i got some time.
was (Author: ggezer):
Hi,
Architecture exposition must be left as it is without putting extra mechanisms
into it to expose ComponentInstance, because that is so much for Architecture's
purpose IMO. But some way to access ComponentInstance and also its lifecycle
events would be clearly an improvement. Factory is surely a place to implement
such mechanism with filtering facility.
And i also think ComponentInstance objects should be registered for every
component created like DeclerativeService does. So client can either use
Factory's facilities or directly access ComponentInstance itself. But that
approach needs a little discussion IMO.
I'll look into this issue as soon as i got some time.
> 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
