Here's what I blogged earlier this morning. JCA is a pain. It's complex, it's subtle, and it's easy to mess up. A better solution would be to define an advisor for any resouce, and generate the necessary JCA interfaces/managedconnections/factories behind the scenes at classload time.
This would work for * JDBC * JMS * Mail * HTTP * Any other resource you want pooled and secure. So far the necessary issues that would have to be addressed in an .xml file would be: * Internally synchronized or externally synchronized Not only could you wrap the resource, you could wrap any Foo (the client retrieval via the resource's getFoo() ). The entire resource graph could be wrapped, similar to how Connection and Statement are wrapped in the current JBossCX implementation. This would allow anyone to turn client code into server code instantly. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3830993#3830993 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3830993 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
