Sorry, my bad. I am using an interceptor. The interceptor derives from
EmtpyInterceptor and implements BeforeTransactionCompletion:
public class BeforeTransactionCompletionInterceptor :
EmptyInterceptor
{
public override void BeforeTransactionCompletion(ITransaction
tx)
{
try
{
... do some stuff
}
catch (Exception ex)
{
tx.Rollback();
throw new FaultException(ex.Message);
}
}
}
thanx,
ramin
On Oct 23, 3:44 pm, Fabio Maulo <[email protected]> wrote:
> I haven't understood which is the event/listener you are using.
>
> 2009/10/23 Ramin <[email protected]>
>
>
>
>
>
> > Hello,
>
> > In BeforeTransactionCompletion I am performing some post-flush-
> > validations and if a validation fails, I roll back the ITransaction
> > with tx.Rollback(). The problem is, that Commit() is still being
> > called on the underlying database connection after tx.Rollback() was
> > called, and I ultimately get an unhandled exception.
>
> > Is this by design? Is it not a good idea to call tx.Rollback() in
> > BeforeTransactionCompletion? If not, what do I use tx for in the
> > BeforeTransactionCompletion-event if not to rollback the transaction?
>
> > I would use the IFlushEventListener, but that can be called more that
> > once, right? So I thought using BeforeTransactionCompletion would be
> > the perfect place to do the post-flush-validations - after everything
> > has been flushed to the database, but before the database transaction
> > has been ultimately commited.
>
> > thanx,
> > ramin
>
> --
> Fabio Maulo
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---
