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
The use case is pretty simple, I had opened a JIRA case some time ago:
http://jira.jboss.com/jira/browse/JBWEB-2
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3861335#3861335
Reply to the post :
Dimitris,
can you point to a detailed description of the Tomcat use case?
Wouldn't it make sense to have independent binding services for TCP/IP and
JNDI? They can have the reverse-dependency with the actual service that
serves the user requests (Tomcat for port 8080).
| bean name=Tomcat
The problem has always been what does mean to be STARTED when
components can be hot deployed.
The current mechanism is to send a notification after the initial install of
conf/jboss-service.xml which means you only get the started once
and there is no notion of stopping.
A better implementation
As Adrian said, this does not work very well. Tomcat waits for that 'server
started' notification, but if you hot deploy it, it doesn't know that the
server is already started.
Depending on another service that represents the server itself would propably
be better.
View the original post :
So just keep the init level around as state somewhere.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3861160#3861160
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3861160
What you could do is let the users define INIT levels and emit a notification
when each of those is reached.
This gives you pre-determined notification, even based on hot-deployed services.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3861137#3861137
Reply
