I picked this from the net...
However, in the context of a larger J2EE application, you'll likely want your
Hibernate objects to take part in an existing JTA transaction. This would be
the normal case if you wanted to access Hibernate objects in a session bean,
for example.
anonymous wrote : JBoss provides the
org.jboss.hibernate.session.HibernateContext class as the integration piece
that does this. The getSession method returns a Hibernate session that is
linked to the current JTA transaction. Naturally this requires that a JTA
transaction exist prior to the call. The following code illustrates the use of
getSession.
|
| Session hsession =
HibernateContext.getSession("java:/hibernate/ExampleEmptorSessionFactory");
| |
| When you get the Hibernate session in this manner, you don't need close the
Hibernate session or manage a hibernate transaction. You can be sure that all
access to the Hibernate session from the current transaction will see the same
state, and you can know that your Hibernate access will be committed to the
database or rolled back along with the larger JTA transaction.
is this the only way....
thnx
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3927381#3927381
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3927381
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
