The more generic issue here is that there is often the desire to have a 
dependency on a collection of services with some quality. Examples include:


Services with network endpoints
Services which interact with the filesystem access
Services which write to the filesystem


Its not always that there should be a true start/stop type of dependency on the 
services.

If there was a snapshot service which periodically backedup the contents of 
serveral directories when the filesystem had no active writers, its not that 
the services which wrote to the filesystem need to be stopped. They simply need 
to be in a state that has no writers. Its more of a lock the snapshot service 
wishes to acquire and will wait until its notified that its the sole holder of 
the lock.

The problem with trying to introduce this notion is that services are not 
generally written with sufficient granularity to allow facets of their behavior 
to be micromanged. The existing JNDI service and a desire to control when 
network interfaces are established is an example. The JNDI service can 
operation fine without an external interface, but the way its coded today, if 
it were to depend on a network interface barrier service to delay the creation 
of its remote JNDI access endpoint, the local operation mode would also be 
unavailable and the server startup would fail horribly as numerous services 
failed to access JNDI via the default InitialContext.


View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864284#3864284

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864284


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to