henk de boer wrote:
Jason Greene wrote:
You can in fact use the spec described @DataSourceDefinition (data-source in xml) to do this. However this uses JDBC directly, since it directly references JDBC classes, and bypasses the JCA layer. So the disadvantage here is that it is an "unmanaged" data source. Anything in the standalone.xml/domain.xml is "managed" and can be added/removed on the fly, monitored, etc.
Hmmm, does "unmanged" in this context also means connections aren't pooled and perhaps aren't suited for use in XA transactions?
By unmanaged I just mean that an administrator couldn't control it which is important to some users.
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. Let us know if you think the spec mechanisms do not meet your needs, and we can start a discussion on the forums about what features are needed. You can actually try out DataSourceDefinition annotation in the beta release right now