[
http://jira.jboss.com/jira/browse/JBSEAM-2702?page=comments#action_12401594 ]
Michael Youngstrom commented on JBSEAM-2702:
--------------------------------------------
In order to use the fix you need to change
platform-transaction-manager="#{someTransactionManager}" or
platform-transaction-manager-name="someTransactionManager" <---not the lack
of expression
Provide mechanism to obtain Spring PlatformTransactionManager
directly from BeanFactory
---------------------------------------------------------------------------------------
Key: JBSEAM-2702
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2702
Project: JBoss Seam
Issue Type: Feature Request
Components: Spring
Affects Versions: 2.1.0.A1
Reporter: Michael Youngstrom
Assigned To: Michael Youngstrom
Fix For: 2.1.0.GA
It appears that when Seam EL searches the JBPM space it creates a transaction. If using
Spring Transactions EL is required to obtain an instance of the Spring
PlatformTransactionManager which then looks in the SeamELResolver before the
SpringELResolver which then causes an infinite loop. Since Transactions are such a core
aspect of Seam I should probably provide a way to get the Spring
PlatformTransactionManager outside of EL to help short circuit such recursive situation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira