[
https://issues.apache.org/jira/browse/OPENJPA-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474323
]
Kevin Sutter commented on OPENJPA-153:
--------------------------------------
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.
> WebSphere and non-jta-data-source and default ManagedRuntime
> ------------------------------------------------------------
>
> Key: OPENJPA-153
> URL: https://issues.apache.org/jira/browse/OPENJPA-153
> Project: OpenJPA
> Issue Type: Improvement
> Components: jdbc
> Environment: WebSphere 6.1
> Reporter: Patrick Linskey
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
