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"> | ... | <reverse-inject name="portManager"> | <method="addListener" startup-level="created"/> | <method="activateRequestsToListener" startup-level="started"/> | <method="suspendRequestsToListener" startup-level="stopped"/> | <method="removeListener" startup-level="destroyed"/> | </reverse-inject> | | </bean> | | related to the lifecycle API thread: http://jboss.com/index.html?module=bb&op=viewtopic&t=58509 To avoid the verbosity of this for each service that binds to a port, a binding interceptor might be appropriate. Ivelin View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861279#3861279 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861279 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
