| Key: |
OPENJPA-153
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Patrick Linskey
|
| Votes: |
0
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
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
|
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.
|
|
Description
|
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. |
Show » |
| No work has yet been logged on this issue.
|
|
