[
https://issues.apache.org/jira/browse/OPENJPA-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-124.
-------------------------------------
Resolution: Won't Fix
Closing as obsolete: JOnAS has no Jakarta EE release. On current servers the
transaction manager is found through the TransactionSynchronizationRegistry
(RegistryManagedRuntime).
> JOnAS integration: OpenJPA should auto-detect the JOnAS transaction manager
> ---------------------------------------------------------------------------
>
> Key: OPENJPA-124
> URL: https://issues.apache.org/jira/browse/OPENJPA-124
> Project: OpenJPA
> Issue Type: New Feature
> Components: third-party
> Environment: JOnAS application server
> Reporter: Patrick Linskey
> Priority: Minor
>
> OpenJPA does not automatically find the TransactionManager when deployed in a
> JOnAS environment. We should modify AutomaticManagedRuntime, either to detect
> JOnAS, or to always look at java:comp/UserTransaction. (JOnAS's
> UserTransaction is also their TransactionManager.)
> See
> http://hanzz.zapto.org/index.php?option=com_content&task=view&id=105&Itemid=31
> for details.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
