[jira] Resolved: (OPENJPA-93) Sequence generation in a JTA environment should not require non-JTA datasource
[ https://issues.apache.org/jira/browse/OPENJPA-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-93. Resolution: Fixed The feature works, but OPENJPA-149 currently prevents it from working in a WebSphere environment in a default configuration. See OPENJPA-149 for a workaround. Sequence generation in a JTA environment should not require non-JTA datasource -- Key: OPENJPA-93 URL: https://issues.apache.org/jira/browse/OPENJPA-93 Project: OpenJPA Issue Type: New Feature Components: jdbc Reporter: Patrick Linskey Assigned To: Patrick Linskey When obtaining non-transactional sequence numbers in a JTA environment when no non-jta-data-source or JDBC connection information is supplied, OpenJPA should suspend the current transaction, perform the sequence maintenance in a new transaction, commit, and resume the suspended transaction. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (OPENJPA-93) Sequence generation in a JTA environment should not require non-JTA datasource
[ http://issues.apache.org/jira/browse/OPENJPA-93?page=all ] Patrick Linskey resolved OPENJPA-93. Resolution: Fixed Added patch with r491148. I did not do any H2-specific testing, however. Sequence generation in a JTA environment should not require non-JTA datasource -- Key: OPENJPA-93 URL: http://issues.apache.org/jira/browse/OPENJPA-93 Project: OpenJPA Issue Type: New Feature Components: jdbc Reporter: Patrick Linskey Assigned To: Patrick Linskey When obtaining non-transactional sequence numbers in a JTA environment when no non-jta-data-source or JDBC connection information is supplied, OpenJPA should suspend the current transaction, perform the sequence maintenance in a new transaction, commit, and resume the suspended transaction. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
