[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-3472) JTASessionContext broken for WebSphere
123 (JIRA)
noreply at atlassian.com
Mon Sep 15 13:38:05 EDT 2008
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31189#action_31189 ]
123 commented on HHH-3472:
--------------------------
I don't use the UserTransaction in my code.
I am using SessionFactory by following the example in
http://www.hibernate.org/hib_docs/reference/en/html/session-configuration.html
SessionFactory sf = new Configuration().configure().buildSessionFactory();
In the hibernate.cfg.xml, I have the property
<property name="hibernate.transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property>
<property name="hibernate.transaction.manager_lookup_class">org.hibernate.transaction.WebSphereTransactionManagerLookup</property>
...
<property name="jta.UserTransaction">java:comp/UserTransaction</property>
Thx.
> JTASessionContext broken for WebSphere
> --------------------------------------
>
> Key: HHH-3472
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3472
> Project: Hibernate Core
> Issue Type: Bug
> Components: core
> Affects Versions: 3.3.0.CR2
> Reporter: Steve Ebersole
> Assignee: Steve Ebersole
> Fix For: 3.3.1, 3.4
>
> Attachments: HHH-3472.patch
>
>
> Basically the notion of "transaction identifier" should have been used in all references to the currentSessionMap, but it was not.
> On a side-note, this is yet another perfect illustration of why some user who actually uses Hibernate on WebSphere should be maintaining all this WebSphere-related code...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list