[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2702) Provide mechanism to obtain Spring PlatformTransactionManager directly from BeanFactory
5:28 p.m.
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.x
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
2:34 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2702) Provide mechanism to obtain Spring PlatformTransactionManager directly from BeanFactory
[ http://jira.jboss.com/jira/browse/JBSEAM-2702?page=all ]
Michael Youngstrom closed JBSEAM-2702.
--------------------------------------
Fix Version/s: 2.1.0.GA
(was: 2.1.x)
Resolution: Done
Fix checked in. Will back port if necessary.
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
9:19 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2702) Provide mechanism to obtain Spring PlatformTransactionManager directly from BeanFactory
[ http://jira.jboss.com/jira/browse/JBSEAM-2702?page=comments#action_12401419 ]
F BI commented on JBSEAM-2702:
------------------------------
Yes, if you could backport it to 2.0.1.GA, that would be great!
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
9:50 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2702) Provide mechanism to obtain Spring PlatformTransactionManager directly from BeanFactory
[ http://jira.jboss.com/jira/browse/JBSEAM-2702?page=comments#action_12401428 ]
Michael Youngstrom commented on JBSEAM-2702:
--------------------------------------------
Can you test this in the latest nightly to be sure it will work for you? If it fixes
you're problem then I will backport it.
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
2:15 a.m.
Hi,
Generated Richfaces stylesheets return empty when requested by browser.
Look at this issue:
http://jira.jboss.com/jira/browse/RF-2316
Apparently we can't use 'login="required"' in pages.xml, because if
we do
so, the stylesheet that is included in the webpage returns empty, when
rendered by the browser.
The people at Richfaces identified this as a SEAM bug, not a Richfaces bug.
Could you please have a look at it. Switching off security is a temporary
workaround, but not a long-term solution.
Thx
Christian
4:47 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2702) Provide mechanism to obtain Spring PlatformTransactionManager directly from BeanFactory
[ http://jira.jboss.com/jira/browse/JBSEAM-2702?page=comments#action_12401544 ]
F BI commented on JBSEAM-2702:
------------------------------
It seems I was to optimistic. No, the problem has not gone with your fix (I tested with
2.1.0-SNAPSHOT from JBoss Snapshot maven repository).
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
9:54 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2702) Provide mechanism to obtain Spring PlatformTransactionManager directly from BeanFactory
[ 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
10:13 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2702) Provide mechanism to obtain Spring PlatformTransactionManager directly from BeanFactory
[ http://jira.jboss.com/jira/browse/JBSEAM-2702?page=comments#action_12401605 ]
F BI commented on JBSEAM-2702:
------------------------------
I used
<spring:spring-transaction
platform-transaction-manager="#{localTransactionManager}"/> in
components.xml
and the spring config is:
<bean id="localTransactionManager"
class="org.springframework.orm.hibernate3.HibernateTransactionManager">
<property name="sessionFactory" ref="hibernateSessionFactory"
/>
</bean>
I was able to isolate the loop in the stacktrace. It is:
at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125)
at org.jboss.seam.Component.callComponentMethod(Component.java:2119)
at org.jboss.seam.Component.unwrap(Component.java:2145)
at org.jboss.seam.Component.getInstance(Component.java:1924)
at org.jboss.seam.Component.getInstance(Component.java:1887)
at org.jboss.seam.Component.getInstance(Component.java:1864)
at org.jboss.seam.Component.getInstance(Component.java:1859)
at org.jboss.seam.bpm.ProcessInstance.instance(ProcessInstance.java:65)
at
org.jboss.seam.contexts.BusinessProcessContext.getProcessInstance(BusinessProcessContext.java:218)
at
org.jboss.seam.contexts.BusinessProcessContext.getContextInstance(BusinessProcessContext.java:205)
at org.jboss.seam.contexts.BusinessProcessContext.get(BusinessProcessContext.java:56)
at org.jboss.seam.contexts.Contexts.lookupInStatefulContexts(Contexts.java:209)
at org.jboss.seam.Component.getInstance(Component.java:1874)
at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:55)
at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:50)
at org.jboss.seam.el.SeamELResolver.resolveBase(SeamELResolver.java:166)
at org.jboss.seam.el.SeamELResolver.getValue(SeamELResolver.java:53)
at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:143)
at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:73)
at org.jboss.el.parser.AstIdentifier.getValue(AstIdentifier.java:44)
at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
at org.jboss.seam.core.Expressions$1.getValue(Expressions.java:112)
at
org.jboss.seam.ioc.spring.SpringTransaction.getPlatformTransactionManager(SpringTransaction.java:91)
at org.jboss.seam.ioc.spring.SpringTransaction.getStatus(SpringTransaction.java:137)
at
org.jboss.seam.transaction.AbstractUserTransaction.isActiveOrMarkedRollback(AbstractUserTransaction.java:32)
at org.jboss.seam.util.Work.workInTransaction(Work.java:27)
at org.jboss.seam.bpm.ProcessInstance.getProcessInstance(ProcessInstance.java:39)
at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source)
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
10:16 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2702) Provide mechanism to obtain Spring PlatformTransactionManager directly from BeanFactory
[ http://jira.jboss.com/jira/browse/JBSEAM-2702?page=comments#action_12401607 ]
Michael Youngstrom commented on JBSEAM-2702:
--------------------------------------------
so change platform-transaction-manager attribute to
platform-transaction-manager-name="localTransactionManager"
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
6:08 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2702) Provide mechanism to obtain Spring PlatformTransactionManager directly from BeanFactory
[ http://jira.jboss.com/jira/browse/JBSEAM-2702?page=comments#action_12401746 ]
F BI commented on JBSEAM-2702:
------------------------------
Yes! That was it. Now it works fine. Thanks a lot!
As soon as I cleaned up and tested it properly, I will publish my work on the
Seam-Spring-jBPM integration.
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
6135
days inactive
6139
days old
9 comments
3 participants
participants (3)
-
Christian Bonami -
F BI (JIRA) -
Michael Youngstrom (JIRA)