[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Influencing component start with DS


Note in this case the immediate component would have to come from the same bundle as the "interesting" component.

-----------------------------------------
Roy Paterson
IBM Pervasive Computing
Austin, TX
Phone: (512) 838-8898



BJ Hargrave/Austin/IBM@IBMUS
Sent by: equinox-dev-bounces@xxxxxxxxxxx

02/23/2006 09:49 AM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

To
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc
Subject
Re: [equinox-dev] Influencing component start with DS





A better way to do this would be to use an immediate component which
enables/disables the interesting component when the criteria is met/unmet.
The details of the criteria could be supplied in component properties of
the immediate component.

BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
hargrave@xxxxxxxxxx
Office: +1 407 849 9117 Mobile: +1 386 848 3788



Roy Paterson/Austin/IBM@IBMUS
Sent by: equinox-dev-bounces@xxxxxxxxxxx
2006-02-23 10:34 AM
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>


To
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc

Subject
Re: [equinox-dev] Influencing component start with DS







There is no interface for hooking in to DS in that way, but you could
implement the same thing with a service.  Your logic could sit in it's own
bundle checking it's criteria.  When the criteria is met it publishes some
dummy service.  The Service Component would be dependent on the service,
so when the service is published the component will be activated.

Roy

-----------------------------------------
Roy Paterson
IBM Pervasive Computing
Austin, TX
Phone: (512) 838-8898



Subbarao Meduri <subbarao_meduri@xxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx
02/23/2006 07:43 AM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>


To
equinox-dev@xxxxxxxxxxx
cc

Subject
[equinox-dev] Influencing component start with DS








Imagine a scenario where a service component should only start if certain
environment
criteria is met. One way to handle this would be that the criteria is
represented as
a property in the component meta-data and the component can use it at
runtime to decide
to shut itself down if the criteria is not met. The downside of such
approach is that
the component code is now contaminated with the criteria.

Is there a mechanism that allows to plug-in additional logic to SCR
runtime to
influence whether a component should be started ?

Regards,
Subbarao

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev


_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev