"mwringe" wrote : | Thats the way the current sar is setup, I can be converted to a -beans.xml in the future. Is there a big reason to switch? | JMX might not be there for 6.x. ;-) Our beans IoC is far superior to our JMX IoC. sar == jar in MC "mwringe" wrote : | Because the deployers are started before the deployables, so I can't inject something from a deployable into a deployer (correct me if I am wrong, but I have tried this) | So I use the MC kernel to get a reference to the objects at runtime which gives me the same result. | It depends how you inject them. ;-) After each phase deploy - boot, deployers, deploy - a MainDeployer::checkComplete is called, to make sure everything is deployed as it should be. But you can make your injections optional, injected via callback. So it will be almost the same as you have now, except that your code will be MC agnostic, hence more flexible. Think POJO. ;-) "mwringe" wrote : | So the common metadata driven approach is the best? | Best is relative term. ;-) But I guess it's good, see our previous 4.x deployers vs. new VDF. "mwringe" wrote : | No, and there are other deployers which need to do similar things (sometimes even worst than the tld deployers). I know its not the best way of doing it, but it works. It something that will need to be looked into more and fixed (if possible). What about if we did this on our own? As it looks like we'll have to wait forever for Remy. :-) Or get ThomasH to ping/push the new JBossAS bosses about this issue, as it's crucial for you guys. I think all we need is a VDF based DirContext + investigate how this affects .tld lookup. There already is a VFS based one, but it's not used due to some legacy Servlet api crap. Perhaps we could make this dynamic, e.g. if we see JBP app use VDFDirContext, else fall back to default. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208870#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...