[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1651) HibernateTransaction: @Transactional + Transaction.setRollbackOnly() issue

[Gavin King (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-1651?page=comments#action_12368708 ] 
            
Gavin King commented on JBSEAM-1651:
------------------------------------

I have an attempted fix in CVS, please try it and let me know.

> HibernateTransaction: @Transactional + Transaction.setRollbackOnly() issue
> --------------------------------------------------------------------------
>
>                 Key: JBSEAM-1651
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1651
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0.BETA1
>         Environment: Tomcat 6.0.13, Hibernate local transactions, Seam CVS 11/07/2007.
>            Reporter: Przemyslaw Jaskierski
>            Priority: Blocker
>             Fix For: 2.0.0.CR1
>
>
> Full story in referenced forum thread (please ignore bogus h:messages problem report).
> !!! Another thing that looks strange is this "registering synchronization: ManagedHibernateSession(java:/seamManagedHibernateSession)" message. This is a "non-JNDI-driven" environment, my components.xml looks like:
> <core:init transaction-management-enabled="true" debug="true"/> 
> <persistence:managed-hibernate-session name="seamManagedHibernateSession" auto-create="true"
>        session-factory="#{sessionFactoryDelegate.sessionFactory}"/>
> <transaction:hibernate-transaction session="#{seamManagedHibernateSession}"/>
> where sessionFactoryDelegate is my STATELESS-scoped Seam component that provides HibernateSessionFactory by getSessionFactory(). This factory is created using Spring from a hibernate.cfg.xml file that has configured JDBC transactions as transaction strategy and then injected to this Seam component at startup. I'm sure it has no meaning here, just want you to have a full picture.

-- 
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