another common approach is to do this

have your txn filter put a transaction handle into a threadlocal, then
in requestcycle.onruntimeexception() you can do :
transactionholder.gettransaction().setrollbackonly(true);

-igor

On Thu, Nov 5, 2009 at 11:59 AM, Igor Vaynberg <igor.vaynb...@gmail.com> wrote:
> check the http response code?
>
> -igor
>
> On Thu, Nov 5, 2009 at 11:20 AM, Steve Lowery
> <slow...@gatessolutions.com> wrote:
>> We have a filter that runs in our context before the wicket filter that
>> starts a hibernate transaction, does a chain.doFilter() and then commits the
>> transaction.  The problem we are running into is that if a RuntimeException
>> is thrown, Wicket catches it, logs it and figures out which page to display
>> to the user.  However, the exception is swallowed and therefore our filter
>> has no knowledge that something bad occurred and is committing the
>> transaction when it shouldn't be.
>>
>> What is the recommended way to deal with this?
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to