openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-153) WebSphere and non-jta-data-source and default ManagedRuntime
Date Mon, 16 Apr 2007 16:12:15 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489156
] 

Michael Dick commented on OPENJPA-153:
--------------------------------------

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. 



> 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
>             Fix For: 0.9.7
>
>
> 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.


Mime
View raw message