[Design of JCA on JBoss] - Re: Programmatic deployment--Redux
by weston.price@jboss.com
Prototype is just about done. The last work involves hooking the DsDeployer into the JMX kernel where the current MBeans (ConnectionManager, Pool etc) can be generated. This actually turned out to be much easier than I originally thought it would be. That was the last real road block.
The *-dsx.xml format pretty much mimics the old format with a few exceptions. Again I want to avoid an either/or approach for this type of stuff. I think it's beneficial to have multiple paths for this type of stuff.
The old XSL deployer will still be around in the case that someone wants to use it so it's not as if we are making a complete break. Once JCA gets rewritten against the JCA 2.0 spec and the new MC stuff I anticipate the XSL deployer fading away.
I was skeptical at first, but I actually like the new deployers/deployment model. It allows for a ton of extension/plugin points that were all but impossible before.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988268#3988268
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988268
19 years, 4 months
[Design of JCA on JBoss] - Re: Programmatic deployment--Redux
by 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
19 years, 4 months