[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[equinox-dev] Influencing component start with DS
- From: Subbarao Meduri <subbarao_meduri@xxxxxxxxx>
- Date: Thu, 23 Feb 2006 05:43:34 -0800 (PST)
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=xOswXrJfKckl6N3KTkvHa2UnVWJazEB9jO/QRbaQvA+cgtAlgrqpiujQpEH5LXEIkTRRyHo5DHhl9mP20+ND0V+DSjVMaQqiClwl1rWJ9srGZK/lnnpnQ3GxjVxgGtcTGRkXMfDTYaFFq/BgLzw7FljWU3PiaMUa9nADM7PEw1Y= ;
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 ?
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around