[ https://jira.jboss.org/jira/browse/JBAS-7813?page=com.atlassian.jira.plug... ] Brian Stansberry commented on JBAS-7813: ---------------------------------------- In the Tomcat module there's actually a o.j.w.tomcat.service.deployers.ClusteringDependencyDeployer that's meant to add such a dependency to <distributable/> webapps. I didn't include it in the AS because the AS supports the behavior where in "default" a <distributable/> webapp will deploy with the JBW StandardManager if clustering support isn't available. Possible solutions: 1) Don't deploy that deployer in "default" -- use a different version of war-deployers-jboss-beans.xml. Yuck. 2) Package stuff like this in its own jboss-beans.xml and don't include in default 3) Detect availability of clustering (i.e. presence of needed classes) in ClusteringDependencyDeployer; don't add dependency if classes aren't there. Thats's a poor separation of concerns. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira