[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1636) Cannot inject Spring-bound HibernateSessionFactory to Seam-managed Hibernate Session
3:11 p.m.
Cannot inject Spring-bound HibernateSessionFactory to Seam-managed Hibernate Session
------------------------------------------------------------------------------------
Key: JBSEAM-1636
URL: http://jira.jboss.com/jira/browse/JBSEAM-1636
Project: JBoss Seam
Issue Type: Bug
Components: Spring
Environment: Tomcat 6.0.13, Spring 2.0.6, Seam CVS 08072007
Reporter: Przemyslaw Jaskierski
Priority: Minor
Attachments: seamComponentNamespaceStackTrace.txt.zip,
springELResolverStackTrace.txt.zip, springStartedFromSeam.txt.zip
Filling this PR as requested by Mike.
For a full story please read related topic. As you requested I tried to reproduce
environment from my previous unsuccessful attempts. It's a little bit frustrating but
after assembling it once again now Spring EL resolver seams to working somewhat in some
aspects. But let's try to report step by step.
1. Spring-EL approach: Spring-bound session factory, referenced in components, Spring EL
resolver put into faces-config. There are two cases:
1.a. I have Seam-session-scoped bean that in @Create tries to get Hibernate session and
retrieve some information from RDBMS. I have abstracted Seam-managed-hibernate-session
access, and this additional layer simply invokes
Component.instance(NAME_OF_SEAM_MANAGED_HIBERNATE_SESSION_COMPONENT_DECLARED_IN_COMPONENTSXML)
instead of relying in @In. This layer is completely pluggable and allows to select
HibernateSession manager (Seam, Spring OSIV, custom one for Test) and inject it into data
access layer.
Ok, so this @Create call renders a bunch of extremely huge stacktreace (WORKED in
Microncontainer/Seam 1.3 combo flawlessly). You can see these stracktraces in
springELResolverStackTrace.txt.zip file.
1.b. Every following HibernateSession access seams to WORK now (I swear It didn't :().
Strange... Anyway I cannot use it because of 1.a.
1.1 components.xml
<persistence:managed-hibernate-session name="seamManagedHibernateSession"
auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
2. Spring namespace approach: Spring-bound session factory, referenced in components.xml,
<seam:component> added to Factory definition in application context:
<bean id="pecpHibernateSessionFactory"
class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"
scope="prototype">
<seam:component class="org.hibernate.impl.SessionFactoryImpl"/>
<property name="dataSource" ref="dataSource" />
<property name="configLocation"
value="classpath:conf/hibernate/hibernate.cfg.xml" />
<property name="configurationClass"
value="org.hibernate.cfg.AnnotationConfiguration"/>
<property name="namingStrategy">
<bean
class="egd.persistence.hibernate.extensions.UnderscoreAwareNamingStrategy"/>
</property>
</bean>
Spring listener put AFTER Seam listener in web.xml. App contexts configured from Spring
listener. Result: java.lang.IllegalStateException: No active application scope. See
seamComponentNamespaceStackTrace.txt.zip.
2.1. components.xml like in 1.1.
3. <spring:context-loader> approach. Everything like in point 2., but Spring
listener removed from web.xml.
Result: "Seam cannot wrap JDK proxied IoC beans. Please use CGLib or Javassist
proxying instead" - stracktrace in
springStartedFromSeam.txt.zip
3.1. components.xml
<core:init transaction-management-enabled="true"
debug="true"/>
<core:manager conversation-timeout="120000"
concurrent-request-timeout="500"
conversation-id-parameter="k"/>
<spring:context-loader config-locations="classpath:conf/spring/core.xml,
classpath:conf/spring/persistence-common.xml,
classpath:conf/spring/persistence-hibernate.xml,
classpath:conf/spring/statistics.xml"/>
<persistence:managed-hibernate-session name="seamManagedHibernateSession"
auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
That's all info I can get about this. Having a model example of such integration that
I was struggling with would be a quite nice POC.
Now I need to get back to code, because I lost a lot of time lately :). Will happy live
with my current workaround for a while :).
--
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
3:11 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1636) Cannot inject Spring-bound HibernateSessionFactory to Seam-managed Hibernate Session
[ http://jira.jboss.com/jira/browse/JBSEAM-1636?page=all ]
Przemyslaw Jaskierski updated JBSEAM-1636:
------------------------------------------
Attachment: springELResolverStackTrace.txt.zip
seamComponentNamespaceStackTrace.txt.zip
springStartedFromSeam.txt.zip
Stacktraces.
Cannot inject Spring-bound HibernateSessionFactory to Seam-managed
Hibernate Session
------------------------------------------------------------------------------------
Key: JBSEAM-1636
URL: http://jira.jboss.com/jira/browse/JBSEAM-1636
Project: JBoss Seam
Issue Type: Bug
Components: Spring
Environment: Tomcat 6.0.13, Spring 2.0.6, Seam CVS 08072007
Reporter: Przemyslaw Jaskierski
Priority: Minor
Attachments: seamComponentNamespaceStackTrace.txt.zip,
springELResolverStackTrace.txt.zip, springStartedFromSeam.txt.zip
Filling this PR as requested by Mike.
For a full story please read related topic. As you requested I tried to reproduce
environment from my previous unsuccessful attempts. It's a little bit frustrating but
after assembling it once again now Spring EL resolver seams to working somewhat in some
aspects. But let's try to report step by step.
1. Spring-EL approach: Spring-bound session factory, referenced in components, Spring EL
resolver put into faces-config. There are two cases:
1.a. I have Seam-session-scoped bean that in @Create tries to get Hibernate session and
retrieve some information from RDBMS. I have abstracted Seam-managed-hibernate-session
access, and this additional layer simply invokes
Component.instance(NAME_OF_SEAM_MANAGED_HIBERNATE_SESSION_COMPONENT_DECLARED_IN_COMPONENTSXML)
instead of relying in @In. This layer is completely pluggable and allows to select
HibernateSession manager (Seam, Spring OSIV, custom one for Test) and inject it into data
access layer.
Ok, so this @Create call renders a bunch of extremely huge stacktreace (WORKED in
Microncontainer/Seam 1.3 combo flawlessly). You can see these stracktraces in
springELResolverStackTrace.txt.zip file.
1.b. Every following HibernateSession access seams to WORK now (I swear It didn't
:(). Strange... Anyway I cannot use it because of 1.a.
1.1 components.xml
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
2. Spring namespace approach: Spring-bound session factory, referenced in components.xml,
<seam:component> added to Factory definition in application context:
<bean id="pecpHibernateSessionFactory"
class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"
scope="prototype">
<seam:component class="org.hibernate.impl.SessionFactoryImpl"/>
<property name="dataSource" ref="dataSource" />
<property name="configLocation"
value="classpath:conf/hibernate/hibernate.cfg.xml" />
<property name="configurationClass"
value="org.hibernate.cfg.AnnotationConfiguration"/>
<property name="namingStrategy">
<bean
class="egd.persistence.hibernate.extensions.UnderscoreAwareNamingStrategy"/>
</property>
</bean>
Spring listener put AFTER Seam listener in web.xml. App contexts configured from Spring
listener. Result: java.lang.IllegalStateException: No active application scope. See
seamComponentNamespaceStackTrace.txt.zip.
2.1. components.xml like in 1.1.
3. <spring:context-loader> approach. Everything like in point 2., but Spring
listener removed from web.xml.
Result: "Seam cannot wrap JDK proxied IoC beans. Please use CGLib or Javassist
proxying instead" - stracktrace in
springStartedFromSeam.txt.zip
3.1. components.xml
<core:init transaction-management-enabled="true"
debug="true"/>
<core:manager conversation-timeout="120000"
concurrent-request-timeout="500"
conversation-id-parameter="k"/>
<spring:context-loader config-locations="classpath:conf/spring/core.xml,
classpath:conf/spring/persistence-common.xml,
classpath:conf/spring/persistence-hibernate.xml,
classpath:conf/spring/statistics.xml"/>
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
That's all info I can get about this. Having a model example of such integration that
I was struggling with would be a quite nice POC.
Now I need to get back to code, because I lost a lot of time lately :). Will happy live
with my current workaround for a while :).
--
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
3:30 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-1636) Cannot inject Spring-bound HibernateSessionFactory to Seam-managed Hibernate Session
[ http://jira.jboss.com/jira/browse/JBSEAM-1636?page=all ]
Michael Youngstrom reassigned JBSEAM-1636:
------------------------------------------
Assignee: Michael Youngstrom
Cannot inject Spring-bound HibernateSessionFactory to Seam-managed
Hibernate Session
------------------------------------------------------------------------------------
Key: JBSEAM-1636
URL: http://jira.jboss.com/jira/browse/JBSEAM-1636
Project: JBoss Seam
Issue Type: Bug
Components: Spring
Environment: Tomcat 6.0.13, Spring 2.0.6, Seam CVS 08072007
Reporter: Przemyslaw Jaskierski
Assigned To: Michael Youngstrom
Priority: Minor
Attachments: seamComponentNamespaceStackTrace.txt.zip,
springELResolverStackTrace.txt.zip, springStartedFromSeam.txt.zip
Filling this PR as requested by Mike.
For a full story please read related topic. As you requested I tried to reproduce
environment from my previous unsuccessful attempts. It's a little bit frustrating but
after assembling it once again now Spring EL resolver seams to working somewhat in some
aspects. But let's try to report step by step.
1. Spring-EL approach: Spring-bound session factory, referenced in components, Spring EL
resolver put into faces-config. There are two cases:
1.a. I have Seam-session-scoped bean that in @Create tries to get Hibernate session and
retrieve some information from RDBMS. I have abstracted Seam-managed-hibernate-session
access, and this additional layer simply invokes
Component.instance(NAME_OF_SEAM_MANAGED_HIBERNATE_SESSION_COMPONENT_DECLARED_IN_COMPONENTSXML)
instead of relying in @In. This layer is completely pluggable and allows to select
HibernateSession manager (Seam, Spring OSIV, custom one for Test) and inject it into data
access layer.
Ok, so this @Create call renders a bunch of extremely huge stacktreace (WORKED in
Microncontainer/Seam 1.3 combo flawlessly). You can see these stracktraces in
springELResolverStackTrace.txt.zip file.
1.b. Every following HibernateSession access seams to WORK now (I swear It didn't
:(). Strange... Anyway I cannot use it because of 1.a.
1.1 components.xml
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
2. Spring namespace approach: Spring-bound session factory, referenced in components.xml,
<seam:component> added to Factory definition in application context:
<bean id="pecpHibernateSessionFactory"
class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"
scope="prototype">
<seam:component class="org.hibernate.impl.SessionFactoryImpl"/>
<property name="dataSource" ref="dataSource" />
<property name="configLocation"
value="classpath:conf/hibernate/hibernate.cfg.xml" />
<property name="configurationClass"
value="org.hibernate.cfg.AnnotationConfiguration"/>
<property name="namingStrategy">
<bean
class="egd.persistence.hibernate.extensions.UnderscoreAwareNamingStrategy"/>
</property>
</bean>
Spring listener put AFTER Seam listener in web.xml. App contexts configured from Spring
listener. Result: java.lang.IllegalStateException: No active application scope. See
seamComponentNamespaceStackTrace.txt.zip.
2.1. components.xml like in 1.1.
3. <spring:context-loader> approach. Everything like in point 2., but Spring
listener removed from web.xml.
Result: "Seam cannot wrap JDK proxied IoC beans. Please use CGLib or Javassist
proxying instead" - stracktrace in
springStartedFromSeam.txt.zip
3.1. components.xml
<core:init transaction-management-enabled="true"
debug="true"/>
<core:manager conversation-timeout="120000"
concurrent-request-timeout="500"
conversation-id-parameter="k"/>
<spring:context-loader config-locations="classpath:conf/spring/core.xml,
classpath:conf/spring/persistence-common.xml,
classpath:conf/spring/persistence-hibernate.xml,
classpath:conf/spring/statistics.xml"/>
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
That's all info I can get about this. Having a model example of such integration that
I was struggling with would be a quite nice POC.
Now I need to get back to code, because I lost a lot of time lately :). Will happy live
with my current workaround for a while :).
--
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
3:34 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1636) Cannot inject Spring-bound HibernateSessionFactory to Seam-managed Hibernate Session
[ http://jira.jboss.com/jira/browse/JBSEAM-1636?page=comments#action_12368469 ]
Michael Youngstrom commented on JBSEAM-1636:
--------------------------------------------
Is there a particular reason why you're trying to make pecpHibernateSessionFactory a
seam component?
When you have time try #3 again but don't do <seam:component/> on
pecpHibernateSessionFactory. that should get rid of the "Seam cannot wrap JDK
proxied IoC beans. Please use CGLib or Javassist proxying instead" error.
Cannot inject Spring-bound HibernateSessionFactory to Seam-managed
Hibernate Session
------------------------------------------------------------------------------------
Key: JBSEAM-1636
URL: http://jira.jboss.com/jira/browse/JBSEAM-1636
Project: JBoss Seam
Issue Type: Bug
Components: Spring
Environment: Tomcat 6.0.13, Spring 2.0.6, Seam CVS 08072007
Reporter: Przemyslaw Jaskierski
Assigned To: Michael Youngstrom
Priority: Minor
Attachments: seamComponentNamespaceStackTrace.txt.zip,
springELResolverStackTrace.txt.zip, springStartedFromSeam.txt.zip
Filling this PR as requested by Mike.
For a full story please read related topic. As you requested I tried to reproduce
environment from my previous unsuccessful attempts. It's a little bit frustrating but
after assembling it once again now Spring EL resolver seams to working somewhat in some
aspects. But let's try to report step by step.
1. Spring-EL approach: Spring-bound session factory, referenced in components, Spring EL
resolver put into faces-config. There are two cases:
1.a. I have Seam-session-scoped bean that in @Create tries to get Hibernate session and
retrieve some information from RDBMS. I have abstracted Seam-managed-hibernate-session
access, and this additional layer simply invokes
Component.instance(NAME_OF_SEAM_MANAGED_HIBERNATE_SESSION_COMPONENT_DECLARED_IN_COMPONENTSXML)
instead of relying in @In. This layer is completely pluggable and allows to select
HibernateSession manager (Seam, Spring OSIV, custom one for Test) and inject it into data
access layer.
Ok, so this @Create call renders a bunch of extremely huge stacktreace (WORKED in
Microncontainer/Seam 1.3 combo flawlessly). You can see these stracktraces in
springELResolverStackTrace.txt.zip file.
1.b. Every following HibernateSession access seams to WORK now (I swear It didn't
:(). Strange... Anyway I cannot use it because of 1.a.
1.1 components.xml
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
2. Spring namespace approach: Spring-bound session factory, referenced in components.xml,
<seam:component> added to Factory definition in application context:
<bean id="pecpHibernateSessionFactory"
class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"
scope="prototype">
<seam:component class="org.hibernate.impl.SessionFactoryImpl"/>
<property name="dataSource" ref="dataSource" />
<property name="configLocation"
value="classpath:conf/hibernate/hibernate.cfg.xml" />
<property name="configurationClass"
value="org.hibernate.cfg.AnnotationConfiguration"/>
<property name="namingStrategy">
<bean
class="egd.persistence.hibernate.extensions.UnderscoreAwareNamingStrategy"/>
</property>
</bean>
Spring listener put AFTER Seam listener in web.xml. App contexts configured from Spring
listener. Result: java.lang.IllegalStateException: No active application scope. See
seamComponentNamespaceStackTrace.txt.zip.
2.1. components.xml like in 1.1.
3. <spring:context-loader> approach. Everything like in point 2., but Spring
listener removed from web.xml.
Result: "Seam cannot wrap JDK proxied IoC beans. Please use CGLib or Javassist
proxying instead" - stracktrace in
springStartedFromSeam.txt.zip
3.1. components.xml
<core:init transaction-management-enabled="true"
debug="true"/>
<core:manager conversation-timeout="120000"
concurrent-request-timeout="500"
conversation-id-parameter="k"/>
<spring:context-loader config-locations="classpath:conf/spring/core.xml,
classpath:conf/spring/persistence-common.xml,
classpath:conf/spring/persistence-hibernate.xml,
classpath:conf/spring/statistics.xml"/>
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
That's all info I can get about this. Having a model example of such integration that
I was struggling with would be a quite nice POC.
Now I need to get back to code, because I lost a lot of time lately :). Will happy live
with my current workaround for a while :).
--
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
3:52 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1636) Cannot inject Spring-bound HibernateSessionFactory to Seam-managed Hibernate Session
[ http://jira.jboss.com/jira/browse/JBSEAM-1636?page=comments#action_12368472 ]
Przemyslaw Jaskierski commented on JBSEAM-1636:
-----------------------------------------------
Yes. Declaring it as a Seam component I wanted to accomplish:
<persistence:managed-hibernate-session name="seamManagedHibernateSession"
auto-create="true"
session-factory="#{pecpHibernateSessionFactory}"/>
in components.xml. Without this managed-hibernate-session tries to search in JNDI because
no such component can be resolved using EL (note: I think that this is alternate approach
to using Spring EL resolver and I'm not enabling it in this case).
BTW Sorry for component naming inconsistencies in examples above - I tried to make my
descriptors cleaner.
Cannot inject Spring-bound HibernateSessionFactory to Seam-managed
Hibernate Session
------------------------------------------------------------------------------------
Key: JBSEAM-1636
URL: http://jira.jboss.com/jira/browse/JBSEAM-1636
Project: JBoss Seam
Issue Type: Bug
Components: Spring
Environment: Tomcat 6.0.13, Spring 2.0.6, Seam CVS 08072007
Reporter: Przemyslaw Jaskierski
Assigned To: Michael Youngstrom
Priority: Minor
Attachments: seamComponentNamespaceStackTrace.txt.zip,
springELResolverStackTrace.txt.zip, springStartedFromSeam.txt.zip
Filling this PR as requested by Mike.
For a full story please read related topic. As you requested I tried to reproduce
environment from my previous unsuccessful attempts. It's a little bit frustrating but
after assembling it once again now Spring EL resolver seams to working somewhat in some
aspects. But let's try to report step by step.
1. Spring-EL approach: Spring-bound session factory, referenced in components, Spring EL
resolver put into faces-config. There are two cases:
1.a. I have Seam-session-scoped bean that in @Create tries to get Hibernate session and
retrieve some information from RDBMS. I have abstracted Seam-managed-hibernate-session
access, and this additional layer simply invokes
Component.instance(NAME_OF_SEAM_MANAGED_HIBERNATE_SESSION_COMPONENT_DECLARED_IN_COMPONENTSXML)
instead of relying in @In. This layer is completely pluggable and allows to select
HibernateSession manager (Seam, Spring OSIV, custom one for Test) and inject it into data
access layer.
Ok, so this @Create call renders a bunch of extremely huge stacktreace (WORKED in
Microncontainer/Seam 1.3 combo flawlessly). You can see these stracktraces in
springELResolverStackTrace.txt.zip file.
1.b. Every following HibernateSession access seams to WORK now (I swear It didn't
:(). Strange... Anyway I cannot use it because of 1.a.
1.1 components.xml
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
2. Spring namespace approach: Spring-bound session factory, referenced in components.xml,
<seam:component> added to Factory definition in application context:
<bean id="pecpHibernateSessionFactory"
class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"
scope="prototype">
<seam:component class="org.hibernate.impl.SessionFactoryImpl"/>
<property name="dataSource" ref="dataSource" />
<property name="configLocation"
value="classpath:conf/hibernate/hibernate.cfg.xml" />
<property name="configurationClass"
value="org.hibernate.cfg.AnnotationConfiguration"/>
<property name="namingStrategy">
<bean
class="egd.persistence.hibernate.extensions.UnderscoreAwareNamingStrategy"/>
</property>
</bean>
Spring listener put AFTER Seam listener in web.xml. App contexts configured from Spring
listener. Result: java.lang.IllegalStateException: No active application scope. See
seamComponentNamespaceStackTrace.txt.zip.
2.1. components.xml like in 1.1.
3. <spring:context-loader> approach. Everything like in point 2., but Spring
listener removed from web.xml.
Result: "Seam cannot wrap JDK proxied IoC beans. Please use CGLib or Javassist
proxying instead" - stracktrace in
springStartedFromSeam.txt.zip
3.1. components.xml
<core:init transaction-management-enabled="true"
debug="true"/>
<core:manager conversation-timeout="120000"
concurrent-request-timeout="500"
conversation-id-parameter="k"/>
<spring:context-loader config-locations="classpath:conf/spring/core.xml,
classpath:conf/spring/persistence-common.xml,
classpath:conf/spring/persistence-hibernate.xml,
classpath:conf/spring/statistics.xml"/>
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
That's all info I can get about this. Having a model example of such integration that
I was struggling with would be a quite nice POC.
Now I need to get back to code, because I lost a lot of time lately :). Will happy live
with my current workaround for a while :).
--
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
3:56 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1636) Cannot inject Spring-bound HibernateSessionFactory to Seam-managed Hibernate Session
[ http://jira.jboss.com/jira/browse/JBSEAM-1636?page=comments#action_12368474 ]
Michael Youngstrom commented on JBSEAM-1636:
--------------------------------------------
You should be able to reference #{pecpHibernateSessionFactory} without making it a seam
component. Part of the Spring+Seam integration is all Spring beans are automatically made
available through EL expressions.
Try taking off the "seam:component" from the SessionFactory and leave
#{pecpHibernateSessionFactory} in components.xml and give it another try.
Cannot inject Spring-bound HibernateSessionFactory to Seam-managed
Hibernate Session
------------------------------------------------------------------------------------
Key: JBSEAM-1636
URL: http://jira.jboss.com/jira/browse/JBSEAM-1636
Project: JBoss Seam
Issue Type: Bug
Components: Spring
Environment: Tomcat 6.0.13, Spring 2.0.6, Seam CVS 08072007
Reporter: Przemyslaw Jaskierski
Assigned To: Michael Youngstrom
Priority: Minor
Attachments: seamComponentNamespaceStackTrace.txt.zip,
springELResolverStackTrace.txt.zip, springStartedFromSeam.txt.zip
Filling this PR as requested by Mike.
For a full story please read related topic. As you requested I tried to reproduce
environment from my previous unsuccessful attempts. It's a little bit frustrating but
after assembling it once again now Spring EL resolver seams to working somewhat in some
aspects. But let's try to report step by step.
1. Spring-EL approach: Spring-bound session factory, referenced in components, Spring EL
resolver put into faces-config. There are two cases:
1.a. I have Seam-session-scoped bean that in @Create tries to get Hibernate session and
retrieve some information from RDBMS. I have abstracted Seam-managed-hibernate-session
access, and this additional layer simply invokes
Component.instance(NAME_OF_SEAM_MANAGED_HIBERNATE_SESSION_COMPONENT_DECLARED_IN_COMPONENTSXML)
instead of relying in @In. This layer is completely pluggable and allows to select
HibernateSession manager (Seam, Spring OSIV, custom one for Test) and inject it into data
access layer.
Ok, so this @Create call renders a bunch of extremely huge stacktreace (WORKED in
Microncontainer/Seam 1.3 combo flawlessly). You can see these stracktraces in
springELResolverStackTrace.txt.zip file.
1.b. Every following HibernateSession access seams to WORK now (I swear It didn't
:(). Strange... Anyway I cannot use it because of 1.a.
1.1 components.xml
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
2. Spring namespace approach: Spring-bound session factory, referenced in components.xml,
<seam:component> added to Factory definition in application context:
<bean id="pecpHibernateSessionFactory"
class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"
scope="prototype">
<seam:component class="org.hibernate.impl.SessionFactoryImpl"/>
<property name="dataSource" ref="dataSource" />
<property name="configLocation"
value="classpath:conf/hibernate/hibernate.cfg.xml" />
<property name="configurationClass"
value="org.hibernate.cfg.AnnotationConfiguration"/>
<property name="namingStrategy">
<bean
class="egd.persistence.hibernate.extensions.UnderscoreAwareNamingStrategy"/>
</property>
</bean>
Spring listener put AFTER Seam listener in web.xml. App contexts configured from Spring
listener. Result: java.lang.IllegalStateException: No active application scope. See
seamComponentNamespaceStackTrace.txt.zip.
2.1. components.xml like in 1.1.
3. <spring:context-loader> approach. Everything like in point 2., but Spring
listener removed from web.xml.
Result: "Seam cannot wrap JDK proxied IoC beans. Please use CGLib or Javassist
proxying instead" - stracktrace in
springStartedFromSeam.txt.zip
3.1. components.xml
<core:init transaction-management-enabled="true"
debug="true"/>
<core:manager conversation-timeout="120000"
concurrent-request-timeout="500"
conversation-id-parameter="k"/>
<spring:context-loader config-locations="classpath:conf/spring/core.xml,
classpath:conf/spring/persistence-common.xml,
classpath:conf/spring/persistence-hibernate.xml,
classpath:conf/spring/statistics.xml"/>
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
That's all info I can get about this. Having a model example of such integration that
I was struggling with would be a quite nice POC.
Now I need to get back to code, because I lost a lot of time lately :). Will happy live
with my current workaround for a while :).
--
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
4:01 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1636) Cannot inject Spring-bound HibernateSessionFactory to Seam-managed Hibernate Session
[ http://jira.jboss.com/jira/browse/JBSEAM-1636?page=comments#action_12368476 ]
Michael Youngstrom commented on JBSEAM-1636:
--------------------------------------------
Also remove the scope on your LocalSessionFactoryBean since it should be a singleon.
Cannot inject Spring-bound HibernateSessionFactory to Seam-managed
Hibernate Session
------------------------------------------------------------------------------------
Key: JBSEAM-1636
URL: http://jira.jboss.com/jira/browse/JBSEAM-1636
Project: JBoss Seam
Issue Type: Bug
Components: Spring
Environment: Tomcat 6.0.13, Spring 2.0.6, Seam CVS 08072007
Reporter: Przemyslaw Jaskierski
Assigned To: Michael Youngstrom
Priority: Minor
Attachments: seamComponentNamespaceStackTrace.txt.zip,
springELResolverStackTrace.txt.zip, springStartedFromSeam.txt.zip
Filling this PR as requested by Mike.
For a full story please read related topic. As you requested I tried to reproduce
environment from my previous unsuccessful attempts. It's a little bit frustrating but
after assembling it once again now Spring EL resolver seams to working somewhat in some
aspects. But let's try to report step by step.
1. Spring-EL approach: Spring-bound session factory, referenced in components, Spring EL
resolver put into faces-config. There are two cases:
1.a. I have Seam-session-scoped bean that in @Create tries to get Hibernate session and
retrieve some information from RDBMS. I have abstracted Seam-managed-hibernate-session
access, and this additional layer simply invokes
Component.instance(NAME_OF_SEAM_MANAGED_HIBERNATE_SESSION_COMPONENT_DECLARED_IN_COMPONENTSXML)
instead of relying in @In. This layer is completely pluggable and allows to select
HibernateSession manager (Seam, Spring OSIV, custom one for Test) and inject it into data
access layer.
Ok, so this @Create call renders a bunch of extremely huge stacktreace (WORKED in
Microncontainer/Seam 1.3 combo flawlessly). You can see these stracktraces in
springELResolverStackTrace.txt.zip file.
1.b. Every following HibernateSession access seams to WORK now (I swear It didn't
:(). Strange... Anyway I cannot use it because of 1.a.
1.1 components.xml
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
2. Spring namespace approach: Spring-bound session factory, referenced in components.xml,
<seam:component> added to Factory definition in application context:
<bean id="pecpHibernateSessionFactory"
class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"
scope="prototype">
<seam:component class="org.hibernate.impl.SessionFactoryImpl"/>
<property name="dataSource" ref="dataSource" />
<property name="configLocation"
value="classpath:conf/hibernate/hibernate.cfg.xml" />
<property name="configurationClass"
value="org.hibernate.cfg.AnnotationConfiguration"/>
<property name="namingStrategy">
<bean
class="egd.persistence.hibernate.extensions.UnderscoreAwareNamingStrategy"/>
</property>
</bean>
Spring listener put AFTER Seam listener in web.xml. App contexts configured from Spring
listener. Result: java.lang.IllegalStateException: No active application scope. See
seamComponentNamespaceStackTrace.txt.zip.
2.1. components.xml like in 1.1.
3. <spring:context-loader> approach. Everything like in point 2., but Spring
listener removed from web.xml.
Result: "Seam cannot wrap JDK proxied IoC beans. Please use CGLib or Javassist
proxying instead" - stracktrace in
springStartedFromSeam.txt.zip
3.1. components.xml
<core:init transaction-management-enabled="true"
debug="true"/>
<core:manager conversation-timeout="120000"
concurrent-request-timeout="500"
conversation-id-parameter="k"/>
<spring:context-loader config-locations="classpath:conf/spring/core.xml,
classpath:conf/spring/persistence-common.xml,
classpath:conf/spring/persistence-hibernate.xml,
classpath:conf/spring/statistics.xml"/>
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
That's all info I can get about this. Having a model example of such integration that
I was struggling with would be a quite nice POC.
Now I need to get back to code, because I lost a lot of time lately :). Will happy live
with my current workaround for a while :).
--
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
4:35 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1636) Cannot inject Spring-bound HibernateSessionFactory to Seam-managed Hibernate Session
[ http://jira.jboss.com/jira/browse/JBSEAM-1636?page=comments#action_12368478 ]
Przemyslaw Jaskierski commented on JBSEAM-1636:
-----------------------------------------------
Mike I've done both things. Still fails. Now I have:
1. AppContext:
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
http://jboss.com/products/seam/spring-seam
http://jboss.com/products/seam/spring-seam-2.0.xsd">
<bean id="pecpHibernateSessionFactory"
class="org.springframework.orm.hibernate3.LocalSessionFactoryBean">
<property name="dataSource" ref="dataSource" />
<property name="configLocation"
value="classpath:conf/hibernate/hibernate.cfg.xml" />
<property name="configurationClass"
value="org.hibernate.cfg.AnnotationConfiguration"/>
<property name="namingStrategy">
<bean
class="edg.persistence.hibernate.extensions.UnderscoreAwareNamingStrategy"/>
</property>
</bean>
2. components.xml
http://jboss.com/products/seam/spring
http://jboss.com/products/seam/spring-2.0.xsd">
<core:init transaction-management-enabled="true"
debug="true"/>
<core:manager conversation-timeout="120000"
concurrent-request-timeout="500"
conversation-id-parameter="k"/>
<spring:context-loader config-locations="classpath:conf/spring/core.xml,
classpath:conf/spring/persistence-common.xml,
classpath:conf/spring/persistence-hibernate.xml,
classpath:conf/spring/statistics.xml"/>
<persistence:managed-hibernate-session
name="pecpSeamManagedHibernateSession" auto-create="true"
session-factory="#{pecpHibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{pecpSeamManagedHibernateSession}"/>
Like I said before I have Session-scoped Seam component which in his @Create method call
indirectly something like:
Session hibernateSession = (Session)
Component.getInstance("pecpSeamManagedHibernateSession");
But in the stacktrace below every piece of my view that tries to get handle to
sessionFactory fails on the same JNDI (?) lookup.
after this Seam produces huge circular rolling stacktrace that basically renders this:
java.lang.IllegalArgumentException: SessionFactory not found in JNDI:
java:/pecpSeamManagedHibernateSession
org.jboss.seam.persistence.ManagedHibernateSession.getSessionFactoryFromJndiOrValueBinding(ManagedHibernateSession.java:238)
org.jboss.seam.persistence.ManagedHibernateSession.initSession(ManagedHibernateSession.java:81)
org.jboss.seam.persistence.ManagedHibernateSession.getSession(ManagedHibernateSession.java:112)
sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:124)
org.jboss.seam.Component.callComponentMethod(Component.java:1974)
org.jboss.seam.Component.unwrap(Component.java:2000)
org.jboss.seam.Component.getInstance(Component.java:1787)
org.jboss.seam.Component.getInstance(Component.java:1740)
org.jboss.seam.Component.getInstance(Component.java:1734)
egd.persistence.hibernate.session.SeamDrivenHibernateSessionProvider.getSession(SeamDrivenHibernateSessionProvider.java:13)
egd.persistence.hibernate.session.HibernateSessionUtil.getSession(HibernateSessionUtil.java:26)
egd.persistence.hibernate.dao.AbstractHibernateDAO.getSession(AbstractHibernateDAO.java:22)
egd.persistence.hibernate.dao.CategoryDAO.getRootCategory(CategoryDAO.java:32)
egd.client.jsf.backers.applicationstate.ApplicationStateBacker.initData(ApplicationStateBacker.java:27)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31)
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
org.jboss.seam.bpm.BusinessProcessInterceptor.aroundInvoke(BusinessProcessInterceptor.java:49)
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42)
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:106)
org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:151)
org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:87)
egd.client.jsf.backers.applicationstate.ApplicationStateBacker_$$_javassist_2.initData(ApplicationStateBacker_$$_javassist_2.java)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:124)
org.jboss.seam.Component.callComponentMethod(Component.java:1974)
org.jboss.seam.Component.callCreateMethod(Component.java:1897)
org.jboss.seam.Component.newInstance(Component.java:1876)
org.jboss.seam.Component.getInstance(Component.java:1773)
org.jboss.seam.Component.getInstance(Component.java:1740)
org.jboss.seam.Component.getInstance(Component.java:1734)
org.jboss.seam.el.SeamELResolver.getValue(SeamELResolver.java:60)
javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53)
com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:64)
org.jboss.el.parser.AstIdentifier.getValue(AstIdentifier.java:44)
org.jboss.el.parser.AstValue.getValue(AstValue.java:63)
org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71)
javax.faces.component.ValueBindingValueExpressionAdapter.getValue(ValueBindingValueExpressionAdapter.java:102)
egd.client.jsf.components.SubcategoriesTreeComponent.getRootCategoryValueBinding(SubcategoriesTreeComponent.java:109)
egd.client.jsf.components.SubcategoriesTreeComponent.encodeEnd(SubcategoriesTreeComponent.java:74)
org.jboss.seam.ui.util.cdk.RendererBase.renderChild(RendererBase.java:190)
org.jboss.seam.ui.util.cdk.RendererBase.renderChildren(RendererBase.java:166)
org.jboss.seam.ui.renderkit.CacheRendererBase.doEncodeChildren(CacheRendererBase.java:59)
org.jboss.seam.ui.util.cdk.RendererBase.encodeChildren(RendererBase.java:92)
javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:812)
javax.faces.component.UIComponent.encodeAll(UIComponent.java:886)
javax.faces.component.UIComponent.encodeAll(UIComponent.java:892)
com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:577)
org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
org.ajax4jsf.framework.ajax.AjaxViewHandler.renderView(AjaxViewHandler.java:233)
com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106)
com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
org.tuckey.web.filters.urlrewrite.NormalRewrittenUrl.doRewrite(NormalRewrittenUrl.java:183)
org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:125)
org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:107)
org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:78)
org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:383)
net.sf.ehcache.constructs.web.filter.GzipFilter.doFilter(GzipFilter.java:75)
net.sf.ehcache.constructs.web.filter.Filter.doFilter(Filter.java:92)
root case:
javax.naming.NamingException: Local server is not initialized
org.jnp.interfaces.LocalOnlyContextFactory.getInitialContext(LocalOnlyContextFactory.java:45)
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
javax.naming.InitialContext.init(InitialContext.java:223)
javax.naming.InitialContext.<init>(InitialContext.java:197)
org.jboss.seam.util.Naming.getInitialContext(Naming.java:37)
org.jboss.seam.util.Naming.getInitialContext(Naming.java:50)
org.jboss.seam.persistence.ManagedHibernateSession.getSessionFactoryFromJndiOrValueBinding(ManagedHibernateSession.java:234)
org.jboss.seam.persistence.ManagedHibernateSession.initSession(ManagedHibernateSession.java:81)
org.jboss.seam.persistence.ManagedHibernateSession.getSession(ManagedHibernateSession.java:112)
sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:124)
org.jboss.seam.Component.callComponentMethod(Component.java:1974)
org.jboss.seam.Component.unwrap(Component.java:2000)
org.jboss.seam.Component.getInstance(Component.java:1787)
org.jboss.seam.Component.getInstance(Component.java:1740)
org.jboss.seam.Component.getInstance(Component.java:1734)
egd.persistence.hibernate.session.SeamDrivenHibernateSessionProvider.getSession(SeamDrivenHibernateSessionProvider.java:13)
egd.persistence.hibernate.session.HibernateSessionUtil.getSession(HibernateSessionUtil.java:26)
egd.persistence.hibernate.dao.AbstractHibernateDAO.getSession(AbstractHibernateDAO.java:22)
egd.persistence.hibernate.dao.CategoryDAO.getRootCategory(CategoryDAO.java:32)
egd.client.jsf.backers.applicationstate.ApplicationStateBacker.initData(ApplicationStateBacker.java:27)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31)
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
org.jboss.seam.bpm.BusinessProcessInterceptor.aroundInvoke(BusinessProcessInterceptor.java:49)
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42)
org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:106)
org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:151)
org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:87)
egd.client.jsf.backers.applicationstate.ApplicationStateBacker_$$_javassist_2.initData(ApplicationStateBacker_$$_javassist_2.java)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:124)
org.jboss.seam.Component.callComponentMethod(Component.java:1974)
org.jboss.seam.Component.callCreateMethod(Component.java:1897)
org.jboss.seam.Component.newInstance(Component.java:1876)
org.jboss.seam.Component.getInstance(Component.java:1773)
org.jboss.seam.Component.getInstance(Component.java:1740)
org.jboss.seam.Component.getInstance(Component.java:1734)
org.jboss.seam.el.SeamELResolver.getValue(SeamELResolver.java:60)
javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53)
com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:64)
org.jboss.el.parser.AstIdentifier.getValue(AstIdentifier.java:44)
org.jboss.el.parser.AstValue.getValue(AstValue.java:63)
org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71)
javax.faces.component.ValueBindingValueExpressionAdapter.getValue(ValueBindingValueExpressionAdapter.java:102)
egd.client.jsf.components.SubcategoriesTreeComponent.getRootCategoryValueBinding(SubcategoriesTreeComponent.java:109)
egd.client.jsf.components.SubcategoriesTreeComponent.encodeEnd(SubcategoriesTreeComponent.java:74)
org.jboss.seam.ui.util.cdk.RendererBase.renderChild(RendererBase.java:190)
org.jboss.seam.ui.util.cdk.RendererBase.renderChildren(RendererBase.java:166)
org.jboss.seam.ui.renderkit.CacheRendererBase.doEncodeChildren(CacheRendererBase.java:59)
org.jboss.seam.ui.util.cdk.RendererBase.encodeChildren(RendererBase.java:92)
javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:812)
javax.faces.component.UIComponent.encodeAll(UIComponent.java:886)
javax.faces.component.UIComponent.encodeAll(UIComponent.java:892)
com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:577)
org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
org.ajax4jsf.framework.ajax.AjaxViewHandler.renderView(AjaxViewHandler.java:233)
com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106)
com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
org.tuckey.web.filters.urlrewrite.NormalRewrittenUrl.doRewrite(NormalRewrittenUrl.java:183)
org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:125)
org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:107)
org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:78)
org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:383)
net.sf.ehcache.constructs.web.filter.GzipFilter.doFilter(GzipFilter.java:75)
net.sf.ehcache.constructs.web.filter.Filter.doFilter(Filter.java:92)
Cannot inject Spring-bound HibernateSessionFactory to Seam-managed
Hibernate Session
------------------------------------------------------------------------------------
Key: JBSEAM-1636
URL: http://jira.jboss.com/jira/browse/JBSEAM-1636
Project: JBoss Seam
Issue Type: Bug
Components: Spring
Environment: Tomcat 6.0.13, Spring 2.0.6, Seam CVS 08072007
Reporter: Przemyslaw Jaskierski
Assigned To: Michael Youngstrom
Priority: Minor
Attachments: seamComponentNamespaceStackTrace.txt.zip,
springELResolverStackTrace.txt.zip, springStartedFromSeam.txt.zip
Filling this PR as requested by Mike.
For a full story please read related topic. As you requested I tried to reproduce
environment from my previous unsuccessful attempts. It's a little bit frustrating but
after assembling it once again now Spring EL resolver seams to working somewhat in some
aspects. But let's try to report step by step.
1. Spring-EL approach: Spring-bound session factory, referenced in components, Spring EL
resolver put into faces-config. There are two cases:
1.a. I have Seam-session-scoped bean that in @Create tries to get Hibernate session and
retrieve some information from RDBMS. I have abstracted Seam-managed-hibernate-session
access, and this additional layer simply invokes
Component.instance(NAME_OF_SEAM_MANAGED_HIBERNATE_SESSION_COMPONENT_DECLARED_IN_COMPONENTSXML)
instead of relying in @In. This layer is completely pluggable and allows to select
HibernateSession manager (Seam, Spring OSIV, custom one for Test) and inject it into data
access layer.
Ok, so this @Create call renders a bunch of extremely huge stacktreace (WORKED in
Microncontainer/Seam 1.3 combo flawlessly). You can see these stracktraces in
springELResolverStackTrace.txt.zip file.
1.b. Every following HibernateSession access seams to WORK now (I swear It didn't
:(). Strange... Anyway I cannot use it because of 1.a.
1.1 components.xml
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
2. Spring namespace approach: Spring-bound session factory, referenced in components.xml,
<seam:component> added to Factory definition in application context:
<bean id="pecpHibernateSessionFactory"
class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"
scope="prototype">
<seam:component class="org.hibernate.impl.SessionFactoryImpl"/>
<property name="dataSource" ref="dataSource" />
<property name="configLocation"
value="classpath:conf/hibernate/hibernate.cfg.xml" />
<property name="configurationClass"
value="org.hibernate.cfg.AnnotationConfiguration"/>
<property name="namingStrategy">
<bean
class="egd.persistence.hibernate.extensions.UnderscoreAwareNamingStrategy"/>
</property>
</bean>
Spring listener put AFTER Seam listener in web.xml. App contexts configured from Spring
listener. Result: java.lang.IllegalStateException: No active application scope. See
seamComponentNamespaceStackTrace.txt.zip.
2.1. components.xml like in 1.1.
3. <spring:context-loader> approach. Everything like in point 2., but Spring
listener removed from web.xml.
Result: "Seam cannot wrap JDK proxied IoC beans. Please use CGLib or Javassist
proxying instead" - stracktrace in
springStartedFromSeam.txt.zip
3.1. components.xml
<core:init transaction-management-enabled="true"
debug="true"/>
<core:manager conversation-timeout="120000"
concurrent-request-timeout="500"
conversation-id-parameter="k"/>
<spring:context-loader config-locations="classpath:conf/spring/core.xml,
classpath:conf/spring/persistence-common.xml,
classpath:conf/spring/persistence-hibernate.xml,
classpath:conf/spring/statistics.xml"/>
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
That's all info I can get about this. Having a model example of such integration that
I was struggling with would be a quite nice POC.
Now I need to get back to code, because I lost a lot of time lately :). Will happy live
with my current workaround for a while :).
--
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
4:44 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1636) Cannot inject Spring-bound HibernateSessionFactory to Seam-managed Hibernate Session
[ http://jira.jboss.com/jira/browse/JBSEAM-1636?page=comments#action_12368480 ]
Michael Youngstrom commented on JBSEAM-1636:
--------------------------------------------
Ok, I think we're getting closer. :) Now do you have the SpringELResolver in your
faces-config.xml? You mentioned in the forum that when you added the ELResolver to your
faces-config you got an infinite loop. Does that happen still?
Cannot inject Spring-bound HibernateSessionFactory to Seam-managed
Hibernate Session
------------------------------------------------------------------------------------
Key: JBSEAM-1636
URL: http://jira.jboss.com/jira/browse/JBSEAM-1636
Project: JBoss Seam
Issue Type: Bug
Components: Spring
Environment: Tomcat 6.0.13, Spring 2.0.6, Seam CVS 08072007
Reporter: Przemyslaw Jaskierski
Assigned To: Michael Youngstrom
Priority: Minor
Attachments: seamComponentNamespaceStackTrace.txt.zip,
springELResolverStackTrace.txt.zip, springStartedFromSeam.txt.zip
Filling this PR as requested by Mike.
For a full story please read related topic. As you requested I tried to reproduce
environment from my previous unsuccessful attempts. It's a little bit frustrating but
after assembling it once again now Spring EL resolver seams to working somewhat in some
aspects. But let's try to report step by step.
1. Spring-EL approach: Spring-bound session factory, referenced in components, Spring EL
resolver put into faces-config. There are two cases:
1.a. I have Seam-session-scoped bean that in @Create tries to get Hibernate session and
retrieve some information from RDBMS. I have abstracted Seam-managed-hibernate-session
access, and this additional layer simply invokes
Component.instance(NAME_OF_SEAM_MANAGED_HIBERNATE_SESSION_COMPONENT_DECLARED_IN_COMPONENTSXML)
instead of relying in @In. This layer is completely pluggable and allows to select
HibernateSession manager (Seam, Spring OSIV, custom one for Test) and inject it into data
access layer.
Ok, so this @Create call renders a bunch of extremely huge stacktreace (WORKED in
Microncontainer/Seam 1.3 combo flawlessly). You can see these stracktraces in
springELResolverStackTrace.txt.zip file.
1.b. Every following HibernateSession access seams to WORK now (I swear It didn't
:(). Strange... Anyway I cannot use it because of 1.a.
1.1 components.xml
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
2. Spring namespace approach: Spring-bound session factory, referenced in components.xml,
<seam:component> added to Factory definition in application context:
<bean id="pecpHibernateSessionFactory"
class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"
scope="prototype">
<seam:component class="org.hibernate.impl.SessionFactoryImpl"/>
<property name="dataSource" ref="dataSource" />
<property name="configLocation"
value="classpath:conf/hibernate/hibernate.cfg.xml" />
<property name="configurationClass"
value="org.hibernate.cfg.AnnotationConfiguration"/>
<property name="namingStrategy">
<bean
class="egd.persistence.hibernate.extensions.UnderscoreAwareNamingStrategy"/>
</property>
</bean>
Spring listener put AFTER Seam listener in web.xml. App contexts configured from Spring
listener. Result: java.lang.IllegalStateException: No active application scope. See
seamComponentNamespaceStackTrace.txt.zip.
2.1. components.xml like in 1.1.
3. <spring:context-loader> approach. Everything like in point 2., but Spring
listener removed from web.xml.
Result: "Seam cannot wrap JDK proxied IoC beans. Please use CGLib or Javassist
proxying instead" - stracktrace in
springStartedFromSeam.txt.zip
3.1. components.xml
<core:init transaction-management-enabled="true"
debug="true"/>
<core:manager conversation-timeout="120000"
concurrent-request-timeout="500"
conversation-id-parameter="k"/>
<spring:context-loader config-locations="classpath:conf/spring/core.xml,
classpath:conf/spring/persistence-common.xml,
classpath:conf/spring/persistence-hibernate.xml,
classpath:conf/spring/statistics.xml"/>
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
That's all info I can get about this. Having a model example of such integration that
I was struggling with would be a quite nice POC.
Now I need to get back to code, because I lost a lot of time lately :). Will happy live
with my current workaround for a while :).
--
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
5 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1636) Cannot inject Spring-bound HibernateSessionFactory to Seam-managed Hibernate Session
[ http://jira.jboss.com/jira/browse/JBSEAM-1636?page=comments#action_12368481 ]
Przemyslaw Jaskierski commented on JBSEAM-1636:
-----------------------------------------------
When I add
<variable-resolver>
org.springframework.web.jsf.DelegatingVariableResolver
</variable-resolver>
to the mix of the configs above I've got exactly the same huge stacktrace including
StackOverflowError like in springELResolverStackTrace.txt.zip
Cannot inject Spring-bound HibernateSessionFactory to Seam-managed
Hibernate Session
------------------------------------------------------------------------------------
Key: JBSEAM-1636
URL: http://jira.jboss.com/jira/browse/JBSEAM-1636
Project: JBoss Seam
Issue Type: Bug
Components: Spring
Environment: Tomcat 6.0.13, Spring 2.0.6, Seam CVS 08072007
Reporter: Przemyslaw Jaskierski
Assigned To: Michael Youngstrom
Priority: Minor
Attachments: seamComponentNamespaceStackTrace.txt.zip,
springELResolverStackTrace.txt.zip, springStartedFromSeam.txt.zip
Filling this PR as requested by Mike.
For a full story please read related topic. As you requested I tried to reproduce
environment from my previous unsuccessful attempts. It's a little bit frustrating but
after assembling it once again now Spring EL resolver seams to working somewhat in some
aspects. But let's try to report step by step.
1. Spring-EL approach: Spring-bound session factory, referenced in components, Spring EL
resolver put into faces-config. There are two cases:
1.a. I have Seam-session-scoped bean that in @Create tries to get Hibernate session and
retrieve some information from RDBMS. I have abstracted Seam-managed-hibernate-session
access, and this additional layer simply invokes
Component.instance(NAME_OF_SEAM_MANAGED_HIBERNATE_SESSION_COMPONENT_DECLARED_IN_COMPONENTSXML)
instead of relying in @In. This layer is completely pluggable and allows to select
HibernateSession manager (Seam, Spring OSIV, custom one for Test) and inject it into data
access layer.
Ok, so this @Create call renders a bunch of extremely huge stacktreace (WORKED in
Microncontainer/Seam 1.3 combo flawlessly). You can see these stracktraces in
springELResolverStackTrace.txt.zip file.
1.b. Every following HibernateSession access seams to WORK now (I swear It didn't
:(). Strange... Anyway I cannot use it because of 1.a.
1.1 components.xml
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
2. Spring namespace approach: Spring-bound session factory, referenced in components.xml,
<seam:component> added to Factory definition in application context:
<bean id="pecpHibernateSessionFactory"
class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"
scope="prototype">
<seam:component class="org.hibernate.impl.SessionFactoryImpl"/>
<property name="dataSource" ref="dataSource" />
<property name="configLocation"
value="classpath:conf/hibernate/hibernate.cfg.xml" />
<property name="configurationClass"
value="org.hibernate.cfg.AnnotationConfiguration"/>
<property name="namingStrategy">
<bean
class="egd.persistence.hibernate.extensions.UnderscoreAwareNamingStrategy"/>
</property>
</bean>
Spring listener put AFTER Seam listener in web.xml. App contexts configured from Spring
listener. Result: java.lang.IllegalStateException: No active application scope. See
seamComponentNamespaceStackTrace.txt.zip.
2.1. components.xml like in 1.1.
3. <spring:context-loader> approach. Everything like in point 2., but Spring
listener removed from web.xml.
Result: "Seam cannot wrap JDK proxied IoC beans. Please use CGLib or Javassist
proxying instead" - stracktrace in
springStartedFromSeam.txt.zip
3.1. components.xml
<core:init transaction-management-enabled="true"
debug="true"/>
<core:manager conversation-timeout="120000"
concurrent-request-timeout="500"
conversation-id-parameter="k"/>
<spring:context-loader config-locations="classpath:conf/spring/core.xml,
classpath:conf/spring/persistence-common.xml,
classpath:conf/spring/persistence-hibernate.xml,
classpath:conf/spring/statistics.xml"/>
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
That's all info I can get about this. Having a model example of such integration that
I was struggling with would be a quite nice POC.
Now I need to get back to code, because I lost a lot of time lately :). Will happy live
with my current workaround for a while :).
--
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
5:24 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1636) Cannot inject Spring-bound HibernateSessionFactory to Seam-managed Hibernate Session
[ http://jira.jboss.com/jira/browse/JBSEAM-1636?page=comments#action_12368486 ]
Michael Youngstrom commented on JBSEAM-1636:
--------------------------------------------
Ok, I think I figured out the infinite loop. Your Session @Create is being called before
the session is actually finished creating. The DelegatingVariableResolver then checks the
faces variables first before checking spring which creates a new session and then calls
your @Create again.
Seam itself should probably be doing something to help inhibit infinite loop Session
scoped @Create calls.
For the time being though all we need to do is get the spring variable resolver to check
spring before it checks JSF. Perhaps my SpringELResovler does this? Try replacing the
DelegatingVariableResolver in faces-config with:
<el-resolver>org.jboss.seam.ioc.spring.SpringELResolver</el-resolver>
Maybe JSF will resolve my ELResolver before the Session resolver.
Cannot inject Spring-bound HibernateSessionFactory to Seam-managed
Hibernate Session
------------------------------------------------------------------------------------
Key: JBSEAM-1636
URL: http://jira.jboss.com/jira/browse/JBSEAM-1636
Project: JBoss Seam
Issue Type: Bug
Components: Spring
Environment: Tomcat 6.0.13, Spring 2.0.6, Seam CVS 08072007
Reporter: Przemyslaw Jaskierski
Assigned To: Michael Youngstrom
Priority: Minor
Attachments: seamComponentNamespaceStackTrace.txt.zip,
springELResolverStackTrace.txt.zip, springStartedFromSeam.txt.zip
Filling this PR as requested by Mike.
For a full story please read related topic. As you requested I tried to reproduce
environment from my previous unsuccessful attempts. It's a little bit frustrating but
after assembling it once again now Spring EL resolver seams to working somewhat in some
aspects. But let's try to report step by step.
1. Spring-EL approach: Spring-bound session factory, referenced in components, Spring EL
resolver put into faces-config. There are two cases:
1.a. I have Seam-session-scoped bean that in @Create tries to get Hibernate session and
retrieve some information from RDBMS. I have abstracted Seam-managed-hibernate-session
access, and this additional layer simply invokes
Component.instance(NAME_OF_SEAM_MANAGED_HIBERNATE_SESSION_COMPONENT_DECLARED_IN_COMPONENTSXML)
instead of relying in @In. This layer is completely pluggable and allows to select
HibernateSession manager (Seam, Spring OSIV, custom one for Test) and inject it into data
access layer.
Ok, so this @Create call renders a bunch of extremely huge stacktreace (WORKED in
Microncontainer/Seam 1.3 combo flawlessly). You can see these stracktraces in
springELResolverStackTrace.txt.zip file.
1.b. Every following HibernateSession access seams to WORK now (I swear It didn't
:(). Strange... Anyway I cannot use it because of 1.a.
1.1 components.xml
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
2. Spring namespace approach: Spring-bound session factory, referenced in components.xml,
<seam:component> added to Factory definition in application context:
<bean id="pecpHibernateSessionFactory"
class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"
scope="prototype">
<seam:component class="org.hibernate.impl.SessionFactoryImpl"/>
<property name="dataSource" ref="dataSource" />
<property name="configLocation"
value="classpath:conf/hibernate/hibernate.cfg.xml" />
<property name="configurationClass"
value="org.hibernate.cfg.AnnotationConfiguration"/>
<property name="namingStrategy">
<bean
class="egd.persistence.hibernate.extensions.UnderscoreAwareNamingStrategy"/>
</property>
</bean>
Spring listener put AFTER Seam listener in web.xml. App contexts configured from Spring
listener. Result: java.lang.IllegalStateException: No active application scope. See
seamComponentNamespaceStackTrace.txt.zip.
2.1. components.xml like in 1.1.
3. <spring:context-loader> approach. Everything like in point 2., but Spring
listener removed from web.xml.
Result: "Seam cannot wrap JDK proxied IoC beans. Please use CGLib or Javassist
proxying instead" - stracktrace in
springStartedFromSeam.txt.zip
3.1. components.xml
<core:init transaction-management-enabled="true"
debug="true"/>
<core:manager conversation-timeout="120000"
concurrent-request-timeout="500"
conversation-id-parameter="k"/>
<spring:context-loader config-locations="classpath:conf/spring/core.xml,
classpath:conf/spring/persistence-common.xml,
classpath:conf/spring/persistence-hibernate.xml,
classpath:conf/spring/statistics.xml"/>
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
That's all info I can get about this. Having a model example of such integration that
I was struggling with would be a quite nice POC.
Now I need to get back to code, because I lost a lot of time lately :). Will happy live
with my current workaround for a while :).
--
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
12:37 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1636) Cannot inject Spring-bound HibernateSessionFactory to Seam-managed Hibernate Session
[ http://jira.jboss.com/jira/browse/JBSEAM-1636?page=comments#action_12368621 ]
Przemyslaw Jaskierski commented on JBSEAM-1636:
-----------------------------------------------
Mike,
after replacing with org.jboss.seam.ioc.spring.SpringELResolver and using
<spring:context-loader> everything works properly, it doesn't enter this nasty
loop.
The same case is when I spawn Spring using the web.xml listener (before Seam listener).
Looks like the org.springframework.web.jsf.DelegatingVariableResolver was the source of
the problem...
Yeaaaaaaaaaaaaaah :)
That saying, to be honest, I feel that it would be better to inject this sessionFactory as
a regular Seam component from the Spring context... Involving extra EL resolver just to be
able to access a single bean doesn't sound right to me, but maybe I should learn
something on how EL resolvers are chained and my concern on involving an extra overhead on
every EL call (houndreds/thousands of them) will disappear...
Thanks for the helping hand, Mike.
Cheeers,
Przemek.
Cannot inject Spring-bound HibernateSessionFactory to Seam-managed
Hibernate Session
------------------------------------------------------------------------------------
Key: JBSEAM-1636
URL: http://jira.jboss.com/jira/browse/JBSEAM-1636
Project: JBoss Seam
Issue Type: Bug
Components: Spring
Environment: Tomcat 6.0.13, Spring 2.0.6, Seam CVS 08072007
Reporter: Przemyslaw Jaskierski
Assigned To: Michael Youngstrom
Priority: Minor
Attachments: seamComponentNamespaceStackTrace.txt.zip,
springELResolverStackTrace.txt.zip, springStartedFromSeam.txt.zip
Filling this PR as requested by Mike.
For a full story please read related topic. As you requested I tried to reproduce
environment from my previous unsuccessful attempts. It's a little bit frustrating but
after assembling it once again now Spring EL resolver seams to working somewhat in some
aspects. But let's try to report step by step.
1. Spring-EL approach: Spring-bound session factory, referenced in components, Spring EL
resolver put into faces-config. There are two cases:
1.a. I have Seam-session-scoped bean that in @Create tries to get Hibernate session and
retrieve some information from RDBMS. I have abstracted Seam-managed-hibernate-session
access, and this additional layer simply invokes
Component.instance(NAME_OF_SEAM_MANAGED_HIBERNATE_SESSION_COMPONENT_DECLARED_IN_COMPONENTSXML)
instead of relying in @In. This layer is completely pluggable and allows to select
HibernateSession manager (Seam, Spring OSIV, custom one for Test) and inject it into data
access layer.
Ok, so this @Create call renders a bunch of extremely huge stacktreace (WORKED in
Microncontainer/Seam 1.3 combo flawlessly). You can see these stracktraces in
springELResolverStackTrace.txt.zip file.
1.b. Every following HibernateSession access seams to WORK now (I swear It didn't
:(). Strange... Anyway I cannot use it because of 1.a.
1.1 components.xml
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
2. Spring namespace approach: Spring-bound session factory, referenced in components.xml,
<seam:component> added to Factory definition in application context:
<bean id="pecpHibernateSessionFactory"
class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"
scope="prototype">
<seam:component class="org.hibernate.impl.SessionFactoryImpl"/>
<property name="dataSource" ref="dataSource" />
<property name="configLocation"
value="classpath:conf/hibernate/hibernate.cfg.xml" />
<property name="configurationClass"
value="org.hibernate.cfg.AnnotationConfiguration"/>
<property name="namingStrategy">
<bean
class="egd.persistence.hibernate.extensions.UnderscoreAwareNamingStrategy"/>
</property>
</bean>
Spring listener put AFTER Seam listener in web.xml. App contexts configured from Spring
listener. Result: java.lang.IllegalStateException: No active application scope. See
seamComponentNamespaceStackTrace.txt.zip.
2.1. components.xml like in 1.1.
3. <spring:context-loader> approach. Everything like in point 2., but Spring
listener removed from web.xml.
Result: "Seam cannot wrap JDK proxied IoC beans. Please use CGLib or Javassist
proxying instead" - stracktrace in
springStartedFromSeam.txt.zip
3.1. components.xml
<core:init transaction-management-enabled="true"
debug="true"/>
<core:manager conversation-timeout="120000"
concurrent-request-timeout="500"
conversation-id-parameter="k"/>
<spring:context-loader config-locations="classpath:conf/spring/core.xml,
classpath:conf/spring/persistence-common.xml,
classpath:conf/spring/persistence-hibernate.xml,
classpath:conf/spring/statistics.xml"/>
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
That's all info I can get about this. Having a model example of such integration that
I was struggling with would be a quite nice POC.
Now I need to get back to code, because I lost a lot of time lately :). Will happy live
with my current workaround for a while :).
--
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
12:43 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1636) Cannot inject Spring-bound HibernateSessionFactory to Seam-managed Hibernate Session
[ http://jira.jboss.com/jira/browse/JBSEAM-1636?page=comments#action_12368622 ]
Przemyslaw Jaskierski commented on JBSEAM-1636:
-----------------------------------------------
LOL, I've just received info about http://jira.jboss.com/jira/browse/JBSEAM-1346.
Apparently this solves my latest concern. Thanks again.
Cannot inject Spring-bound HibernateSessionFactory to Seam-managed
Hibernate Session
------------------------------------------------------------------------------------
Key: JBSEAM-1636
URL: http://jira.jboss.com/jira/browse/JBSEAM-1636
Project: JBoss Seam
Issue Type: Bug
Components: Spring
Environment: Tomcat 6.0.13, Spring 2.0.6, Seam CVS 08072007
Reporter: Przemyslaw Jaskierski
Assigned To: Michael Youngstrom
Priority: Minor
Attachments: seamComponentNamespaceStackTrace.txt.zip,
springELResolverStackTrace.txt.zip, springStartedFromSeam.txt.zip
Filling this PR as requested by Mike.
For a full story please read related topic. As you requested I tried to reproduce
environment from my previous unsuccessful attempts. It's a little bit frustrating but
after assembling it once again now Spring EL resolver seams to working somewhat in some
aspects. But let's try to report step by step.
1. Spring-EL approach: Spring-bound session factory, referenced in components, Spring EL
resolver put into faces-config. There are two cases:
1.a. I have Seam-session-scoped bean that in @Create tries to get Hibernate session and
retrieve some information from RDBMS. I have abstracted Seam-managed-hibernate-session
access, and this additional layer simply invokes
Component.instance(NAME_OF_SEAM_MANAGED_HIBERNATE_SESSION_COMPONENT_DECLARED_IN_COMPONENTSXML)
instead of relying in @In. This layer is completely pluggable and allows to select
HibernateSession manager (Seam, Spring OSIV, custom one for Test) and inject it into data
access layer.
Ok, so this @Create call renders a bunch of extremely huge stacktreace (WORKED in
Microncontainer/Seam 1.3 combo flawlessly). You can see these stracktraces in
springELResolverStackTrace.txt.zip file.
1.b. Every following HibernateSession access seams to WORK now (I swear It didn't
:(). Strange... Anyway I cannot use it because of 1.a.
1.1 components.xml
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
2. Spring namespace approach: Spring-bound session factory, referenced in components.xml,
<seam:component> added to Factory definition in application context:
<bean id="pecpHibernateSessionFactory"
class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"
scope="prototype">
<seam:component class="org.hibernate.impl.SessionFactoryImpl"/>
<property name="dataSource" ref="dataSource" />
<property name="configLocation"
value="classpath:conf/hibernate/hibernate.cfg.xml" />
<property name="configurationClass"
value="org.hibernate.cfg.AnnotationConfiguration"/>
<property name="namingStrategy">
<bean
class="egd.persistence.hibernate.extensions.UnderscoreAwareNamingStrategy"/>
</property>
</bean>
Spring listener put AFTER Seam listener in web.xml. App contexts configured from Spring
listener. Result: java.lang.IllegalStateException: No active application scope. See
seamComponentNamespaceStackTrace.txt.zip.
2.1. components.xml like in 1.1.
3. <spring:context-loader> approach. Everything like in point 2., but Spring
listener removed from web.xml.
Result: "Seam cannot wrap JDK proxied IoC beans. Please use CGLib or Javassist
proxying instead" - stracktrace in
springStartedFromSeam.txt.zip
3.1. components.xml
<core:init transaction-management-enabled="true"
debug="true"/>
<core:manager conversation-timeout="120000"
concurrent-request-timeout="500"
conversation-id-parameter="k"/>
<spring:context-loader config-locations="classpath:conf/spring/core.xml,
classpath:conf/spring/persistence-common.xml,
classpath:conf/spring/persistence-hibernate.xml,
classpath:conf/spring/statistics.xml"/>
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
That's all info I can get about this. Having a model example of such integration that
I was struggling with would be a quite nice POC.
Now I need to get back to code, because I lost a lot of time lately :). Will happy live
with my current workaround for a while :).
--
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
12:51 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1636) Cannot inject Spring-bound HibernateSessionFactory to Seam-managed Hibernate Session
[ http://jira.jboss.com/jira/browse/JBSEAM-1636?page=all ]
Michael Youngstrom closed JBSEAM-1636.
--------------------------------------
Fix Version/s: 2.0.0.CR1
Resolution: Done
It wasn't necessarily org.springframework.web.jsf.DelegatingVariableResolver it was
some strange problem with trying to access the session while a session was in the process
of being created??? I tried to duplicate the problem but was unsuccessful in the latest
nightly so perhaps it has already been fixed. Anyway, glad the SpringELResolver worked
for you.
Mike
Cannot inject Spring-bound HibernateSessionFactory to Seam-managed
Hibernate Session
------------------------------------------------------------------------------------
Key: JBSEAM-1636
URL: http://jira.jboss.com/jira/browse/JBSEAM-1636
Project: JBoss Seam
Issue Type: Bug
Components: Spring
Environment: Tomcat 6.0.13, Spring 2.0.6, Seam CVS 08072007
Reporter: Przemyslaw Jaskierski
Assigned To: Michael Youngstrom
Priority: Minor
Fix For: 2.0.0.CR1
Attachments: seamComponentNamespaceStackTrace.txt.zip,
springELResolverStackTrace.txt.zip, springStartedFromSeam.txt.zip
Filling this PR as requested by Mike.
For a full story please read related topic. As you requested I tried to reproduce
environment from my previous unsuccessful attempts. It's a little bit frustrating but
after assembling it once again now Spring EL resolver seams to working somewhat in some
aspects. But let's try to report step by step.
1. Spring-EL approach: Spring-bound session factory, referenced in components, Spring EL
resolver put into faces-config. There are two cases:
1.a. I have Seam-session-scoped bean that in @Create tries to get Hibernate session and
retrieve some information from RDBMS. I have abstracted Seam-managed-hibernate-session
access, and this additional layer simply invokes
Component.instance(NAME_OF_SEAM_MANAGED_HIBERNATE_SESSION_COMPONENT_DECLARED_IN_COMPONENTSXML)
instead of relying in @In. This layer is completely pluggable and allows to select
HibernateSession manager (Seam, Spring OSIV, custom one for Test) and inject it into data
access layer.
Ok, so this @Create call renders a bunch of extremely huge stacktreace (WORKED in
Microncontainer/Seam 1.3 combo flawlessly). You can see these stracktraces in
springELResolverStackTrace.txt.zip file.
1.b. Every following HibernateSession access seams to WORK now (I swear It didn't
:(). Strange... Anyway I cannot use it because of 1.a.
1.1 components.xml
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
2. Spring namespace approach: Spring-bound session factory, referenced in components.xml,
<seam:component> added to Factory definition in application context:
<bean id="pecpHibernateSessionFactory"
class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"
scope="prototype">
<seam:component class="org.hibernate.impl.SessionFactoryImpl"/>
<property name="dataSource" ref="dataSource" />
<property name="configLocation"
value="classpath:conf/hibernate/hibernate.cfg.xml" />
<property name="configurationClass"
value="org.hibernate.cfg.AnnotationConfiguration"/>
<property name="namingStrategy">
<bean
class="egd.persistence.hibernate.extensions.UnderscoreAwareNamingStrategy"/>
</property>
</bean>
Spring listener put AFTER Seam listener in web.xml. App contexts configured from Spring
listener. Result: java.lang.IllegalStateException: No active application scope. See
seamComponentNamespaceStackTrace.txt.zip.
2.1. components.xml like in 1.1.
3. <spring:context-loader> approach. Everything like in point 2., but Spring
listener removed from web.xml.
Result: "Seam cannot wrap JDK proxied IoC beans. Please use CGLib or Javassist
proxying instead" - stracktrace in
springStartedFromSeam.txt.zip
3.1. components.xml
<core:init transaction-management-enabled="true"
debug="true"/>
<core:manager conversation-timeout="120000"
concurrent-request-timeout="500"
conversation-id-parameter="k"/>
<spring:context-loader config-locations="classpath:conf/spring/core.xml,
classpath:conf/spring/persistence-common.xml,
classpath:conf/spring/persistence-hibernate.xml,
classpath:conf/spring/statistics.xml"/>
<persistence:managed-hibernate-session
name="seamManagedHibernateSession" auto-create="true"
session-factory="#{hibernateSessionFactory}"/>
<transaction:hibernate-transaction
session="#{seamManagedHibernateSession}"/>
That's all info I can get about this. Having a model example of such integration that
I was struggling with would be a quite nice POC.
Now I need to get back to code, because I lost a lot of time lately :). Will happy live
with my current workaround for a while :).
--
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
6171
days inactive
6172
days old
13 comments
2 participants
participants (2)
-
Michael Youngstrom (JIRA) -
Przemyslaw Jaskierski (JIRA)