Weston, Alexey, I want to synch up on the near term roadmap items since I'm looking at working with the jca deployers to flesh out the data source management changes. Here is what Weston mentioned. Can we get jira issues for these and focus on getting 2 done? 1) Complete the new deployment model for JBoss5 Most of this work has been completed. The *-ds.xml deployment format has been put into an XSD and the new deployment stuff 'works' (JAXB based). There were issues with hot deployment that I didn't get a chance to look at. The JCAMetaDataRepository is up and running but really needs some work to become fully functional. 2) Pull JCA out of JBossAS This is simply Maven based build/deployment stuff. JCA should follow with EJB3 in this regard. The legacy JCA implementation should stay in place while this is going on and then things can simply be switched over 3) Core JCA This is the big one. Currently there is a JCA/MC prototype in CVS that captures a skeleton of how JCA would look in the MC. This needs to be fleshed out and ported into JBoss5 proper. 4) Adapters In conjunction with #2, the adapter set needs to be pulled out of AS *and* given its own release cycle/model. JCA core and the JCA adapters should independent of one another. One of the problems that plagued legacy JCA was the cross pollination between the two code bases (ie Remote DataSources). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050574#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...