"scott.stark(a)jboss.org" wrote : I don't think it matters currently as this will have to be updated for the migration of the deployers to the VDF update. I'm close to having jboss boot with the mc/vdf. | I'm guessing you mean that it doesn't matter if I hack up the deployer...Web deployer needs a lot of reorganization anyways to do the dependency resolving that the EJB3 container currently already does. What about the metadata though? I'm currently thinking to go back and use org.jboss.metadata classes instead of creating a new hierarchy. There's just too much code that depends on those metadata classes that would really suck to touch just to get this JavaEE5 integration in for Tomcat (Webservices for example). We'll also want to try and reuse the old EJB 2.1 BMP/CMP containers for EJB 3.0. The other idea is to just reparse web.xml with the new hierarchy and just hack it in. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957885#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...