[jboss-dev-forums] [Design of JCA on JBoss] - Re: Programmatic deployment--Redux

[weston.price@jboss.com]

In this case unfortunately, the classes change quite a bit. Pooling parameters, tx behavior are evolving in JCA from release to release. The *-dsx.xml format would have to accomodate this. The EE descriptors of course are tied to Sun and those are somewhat static, but for JCA configurablity is key. Currently when stuff like this changes we rely on the XSL but that obviously is going to go away for JBoss5. 

In reality, I plan to support a variety of parsers/binders

JAXP
XB
JAXB

It's my plan to provide the metadata classes as a standalone client jar to allow for programmatic deployment and JAXB seemed to make this easier wherein I can version off the XSD rather than having to maintain the binary files in SVN. 

At the very least, evolving the *-ds.xml format from the crap we have today to an actual XSD will make this easier regardless of what binding framework is in use. I think that is the real point I am trying to make. 






View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988264#3988264

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988264