There will be a different way to do that...
On Apr 7, 2015 10:17 AM, "Gunnar Morling" wrote:
> > 4) Transaction is now a single impl. The distinctions are all handled
> internally. TransactionImplementor is gone too
>
> Can OGM still register a custom TransactionFactory? We'd need that in
> ord
> 4) Transaction is now a single impl. The distinctions are all handled
internally. TransactionImplementor is gone too
Can OGM still register a custom TransactionFactory? We'd need that in order
to return our "NoSQL-local" transaction implementation.
2015-04-07 16:27 GMT+02:00 Steve Ebersole
Ok, not hearing any feedback on this so I will proceed as outlined here.
On Wed, Mar 25, 2015 at 3:15 PM, Steve Ebersole wrote:
> We also identified needs for Status#ROLLING_BACK and Status#COMMITTING, so
> consider those in the enum as well.
>
> On Wed, Mar 25, 2015 at 12:19 PM, Steve Ebersole
We also identified needs for Status#ROLLING_BACK and Status#COMMITTING, so
consider those in the enum as well.
On Wed, Mar 25, 2015 at 12:19 PM, Steve Ebersole
wrote:
> I thought I had asked this before, but maybe not. Andrea and I are
> working through the transaction/jdbc changes and I really
I thought I had asked this before, but maybe not. Andrea and I are working
through the transaction/jdbc changes and I really would like to clean up
the org.hibernate.Transaction API. But before I start cutting I wanted to
make sure noone is using the methods I plan on getting rid of...
Here is t
I would fence on the conservative side here, even for isActive and raise an
exception. If it's UNKNOWN, well then we don't know and we can't answer true
nor false. Kind of a Gödelian dilemma ;)
On 29 sept. 2010, at 19:53, Steve Ebersole wrote:
> On Wed, 2010-09-29 at 14:26 +0200, Emmanuel Berna
On Wed, 2010-09-29 at 14:26 +0200, Emmanuel Bernard wrote:
> When are these two case happening:
> - no UT nor TM => looks like a config issue. Other reasons?
For the TM, yes that is the reason in all cases I can think of. For UT,
not necessarily; it depends on whether UT is treated per-thread or
Good points.
When are these two case happening:
- no UT nor TM => looks like a config issue. Other reasons?
- UNKNOWN => aren't things about to hit the fan in this case? Or is there some
acceptable use cases?
On 28 sept. 2010, at 18:53, Steve Ebersole wrote:
> In that case what would you like
In that case what would you like to see happen when say
Transaction.isActive() is called but the UserTransaction or
TransactionManager cannot be found? Or when they report that the status
is UNKOWN? Currently we throw exceptions in both of those cases which
is do not think is uber-useful.
In th
Getting the underlying tx state is more useful to me.
On 28 sept. 2010, at 05:49, Steve Ebersole wrote:
> Currently there is a big discrepancy between the documentation for some
> of the methods on org.hibernate.Transaction and the actual code.
> Specifically the methods isActive(), wasRolledBack
Currently there is a big discrepancy between the documentation for some
of the methods on org.hibernate.Transaction and the actual code.
Specifically the methods isActive(), wasRolledBack() and wasCommitted()
explicitly state that they only account for the "local state" of the
transaction object, n
11 matches
Mail list logo
