That gets us back to the original issue then -- declaring in the WarDeployer bean a
dependency on the TomcatClusteringCache causes the start of the AS to fail due to a
missing dependency, I believe before the VFSDeploymentScanner is even created/started.
The WarDeployer bean also has a commented-out dependency on CachedConnectionManager. If
that were uncommented, I expect the same problem would arise. In both that and the
ClusteredSSO case, it's not the webapp that has the dependency; it's the embedded
Tomcat service itself.
Is a deployer installed via the deployers dir meant to be allowed to have a dependency on
a bean installed from the deploy dir?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982195#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...