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:30:05 UTC
[jira] Created: (OPENJPA-153) WebSphere and non-jta-data-source and
default ManagedRuntime
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: kernel
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.
[jira] Updated: (OPENJPA-153) WebSphere and non-jta-data-source and
default ManagedRuntime
Posted by "Patrick Linskey (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (OPENJPA-153) WebSphere and non-jta-data-source
and default ManagedRuntime
Posted by "Patrick Linskey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Linskey resolved OPENJPA-153.
-------------------------------------
Resolution: Fixed
I believe that the only remaining issue here is captured in OPENJPA-149.
> 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.
[jira] Updated: (OPENJPA-153) WebSphere and non-jta-data-source and
default ManagedRuntime
Posted by "Patrick Linskey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Linskey updated OPENJPA-153:
------------------------------------
Fix Version/s: 0.9.7
> 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.
[jira] Commented: (OPENJPA-153) WebSphere and non-jta-data-source
and default ManagedRuntime
Posted by "Kevin Sutter (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (OPENJPA-153) WebSphere and non-jta-data-source
and default ManagedRuntime
Posted by "Michael Dick (JIRA)" <ji...@apache.org>.
[ 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.