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

[Roy Paterson <rpatersn@xxxxxxxxxx>]

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