henk de boer wrote:
Jason Greene wrote:
It all depends on what jdbc Resource class you point the annotation/xml too. If you point it to a driver XADatasource you get XA, to a PooledDataSource you get connection pooling.
Okay, I had some problems with this in JBoss AS 6, but I'll try again in AS7. Nevertheless, this does mean my DB driver (or other external code) needs to implement the pooling (PooledDataSource). Using this mechanism I won't automatically get the connection pooling provided by JBoss AS, will I?
Also, David Lloyd hinted that a 'regular' (jboss) datasource definition inside an EAR might still be supported (without the ability of an administrator to control it). Can anyone comment on that?
No plans as of yet. If someone can provide a good use case why the general EE stuff can't be used then we can do it. Not very likely for 7.0 though unless someone wants to contribute. It would certainly be unmanaged.
.