We don't need a separate file due to the cluster defaults deployer; having two
different files in the tomcat module is a bit of legacy cruft. A file with the clustering
deployers in it should work just fine in default.
That said, I'd like the clustering deployer out of the file too. IIRC it mostly
isn't because I somewhat wanted the deployer in jbossweb.deployer/META-INF folder and
if I put a second -beans.xml there it wouldn't get deployed.
Re: the various test-config stuff, yes, there has to be a cleverer way. The biggest case
of using a test-config to override instead of add is to change server.xml. A couple do
that to inject sso valves; that can probably be done with a separate mbean instead. Not
particularly "clever", but will work. Don't know if that kind of thing can
be done with some of the others, which try to override stuff like connectors and the
security realm, which may not be changeable after the web server starts.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139878#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...