You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Patrick Linskey (JIRA)" <ji...@apache.org> on 2007/02/16 17:42:05 UTC

[jira] Updated: (OPENJPA-153) WebSphere and non-jta-data-source and default ManagedRuntime

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

Patrick Linskey updated OPENJPA-153:
------------------------------------

    Component/s:     (was: kernel)
                 jdbc

> 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.