On Wed, Jun 13, 2012 at 4:32 PM, fabiolf <[email protected]> wrote:
> Hi Göktürk,
>
>
> Göktürk Gezer wrote
> >
> > You can also use filtering on your Archtitecture requirement like
> > "(architecture.instate=your_instance_name)".
> > Then only your intended instance's Architecture reference will be
> injected
> > into your Array, or you can use just single reference.
> >
> > As i understand your situation, something like following may help:
> >
> > @Bind(filter="(architecture.instance=your_instance_name)")
> > public void bind_instance(Architecture arch)
> > {
> > // Will be called when instance having specified "your_instance_name"
> > is activated with its Architecture reference.
> > }
> >
>
> Thanks for your suggestion, but I don't know previously the instance name I
> will have to look for. So I think the only way is to maintain a copy of all
> instances Architecture references, letting iPOJO simply bind everything in
> that array, and I analyze each one of them to find the one I need, when I
> need to do that. I was hoping I there was some method in a central
> "manager"
> class or something like that, that could give me informations about the
> instance by passing the instance name as a parameter.
>
> But your suggestion gave me an idea for another problem I am having. I
> forgot I could create a callback method for the binding of an specific
> field. That will help a lot! Thanks! :)
>
Yeah, just bind a method to your Architecture[] array then, and analyze it
everytime it changes.
And as this topic is active on
https://issues.apache.org/jira/browse/FELIX-3537 maybe more and more
mechanism those can help you might pop out.
>
> Regards
> Fabio
>
> --
> View this message in context:
> http://apache-felix.18485.n6.nabble.com/How-to-get-the-ComponentInstance-from-the-instance-name-attribute-tp4997990p4998045.html
> Sent from the Apache Felix - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>