yes, u r right.
when i originally tried that, i didn't have the session.commit, as it didn't
make sense to have to call commit on the session when u calling commit on
the ejb transaction. it was after this that i looked through the hibernate
code and saw the need to flush the session.
i think the most misleading thing is the use of the commit method in this
scenario. off the top of my head, i can think of two things that might
improve this situation:
1. add a public flush method to the session that flushes the session.
2. a property to modify the behaviour of the session so that statements are
executed immediately. i guess this would result in sub-optimal performance
in the case of multiple operations in the same session..
brad
----- Original Message -----
From: <Gavin_King/Cirrus%CI...@ci...>
To: "Brad Clow" <bra...@wo...>
Cc: <hib...@li...>
Sent: Wednesday, February 27, 2002 5:32 PM
Subject: Re: [Hibernate-devel] EJB Transactions
>
> Hi Brad :)
>
> You need to set the property
>
> hibernate.auto_commit=false
>
> then you will get the behaviour you are looking for.
>
> This is (poorly) documented. I will try to make it more explicit. Its also
> poorly named .... whats a better name for it?
>
> peace
>
>
|
