[#OPENJPA-153] WebSphere and non-jta-data-source and default ManagedRuntime

OpenJPA

WebSphere and non-jta-data-source and default ManagedRuntime

Created: 16/Feb/07 04:28 PM Updated: 16/Apr/07 04:12 PM

Return to search

Component/s:

jdbc

Affects Version/s:

None

Fix Version/s:

0.9.7

Time Tracking:

Not Specified

Environment:

WebSphere 6.1

Issue Links:

Reference

This issue relates to:

~~OPENJPA-144~~ JDBCConfigurationImpl does not support JNDI lookup for non-jta-data-source.

This issue is related to:

~~OPENJPA-149~~ non-jta-data-source must be specified in WebSphere environments

Resolution Date:

01/Mar/07 01:14 AM

Description

« Hide

See ~~OPENJPA-144~~. It would seem that in a WebSphere environment, when specifying a non-jta-data-source, the JDBC connection that OpenJPA looks up does not permit calls to Connection.commit(). This, in conjunction with ~~OPENJPA-149~~, means that in a default configuration, OpenJPA cannot use non-JTA data sources in a WebSphere environment.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

[ Permlink | « Hide ]

Kevin Sutter added a comment - 20/Feb/07 12:50 AM

This is a temporary situation. WebSphere has always had the convention of "managed" datasources. All datasources would automatically be enlisted in the enclosing transaction. With the introduction of the non-jta-data-source in JPA, WebSphere will need to relax this requirement. Supposedly, the support for the non-jta-data-source will be available in the next Beta of the EJB3 Feature Pack.

[ Permlink | « Hide ]

Patrick Linskey added a comment - 01/Mar/07 01:14 AM

I believe that the only remaining issue here is captured in ~~OPENJPA-149~~.

[ Permlink | « Hide ]

Michael Dick added a comment - 16/Apr/07 04:12 PM

Confirming Kevin's comments above, support for non-jta-datasources is working and will be included in the next release of the WebSphere EJB3 feature pack.