[ http://issues.apache.org/jira/browse/OPENJPA-93?page=comments#action_12461464 ] Patrick Linskey commented on OPENJPA-93: ----------------------------------------
svn r491147 includes code changes that have been tested in WebLogic Server. The feature is not yet documented. The behavior is as follows: if no non-JTA datasource is available and the current environment is managed, OpenJPA will suspend the current transaction, begin a new transaction, do the sequence work, commit, and resume the original transaction. This code makes some thread-safety assumptions that should be valid in a JTA environment, since JTA transactions are inherently thread-bound. > 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
