[
https://issues.apache.org/jira/browse/FELIX-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293920#comment-13293920
]
Fabio Lattario Fonseca commented on FELIX-3537:
-----------------------------------------------
Hi Guillaume,
I'm having a similar problem. I want to access an instance, created by the
framework, through its name, that is unique. I thought that I could issue a
call to some getInstance() somewhere using its name, but I couldn't find these
method.
I'm no iPOJO specialist (far from that!) but, looking inside iPOJO classes,
maybe we can find someone that plays a central role like BundleContext does for
OSGi. Or, perhaps, promote some class to that central role. I saw some
promising classes like IPojoContext. But then this class would have to be
accessible from everywhere, like BundleContext is and I think this can break
some design decisions made in the beginning.
So, to put this method in the Factory may be the right thing to do. But I think
that would not solve my problem.
Well, I don't know... I'll think more...
Regards,
Fabio
> 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
