-Igor
On 12/16/05, John Patterson <[EMAIL PROTECTED]> wrote:
On Friday 16 Dec 2005 18:35, Igor Vaynberg wrote:
> the full name of the interface is:
> wicket.request.compound.IExceptionResponseStrategy.
Cheers. I just did a cvs update and there it was! Wow, a lot has changed.
One small thing - the implementation of IExceptionResponseStrategy. is named
DefaultExceptionResponseProcessor. Missed during refactoring?
> if your
> implementation throws a runtime exception it will get to your filter
> because there are no try/catch blocks in wicket to catch it at that point.
The problem is that when an exception is thrown I want to rollback my
transaction AND then use wickets handy exception handling behaviour.
> we already fully support what you want.
If I simply throw the exception then I have skipped the redirect to the error
page etc.
So again I am in the same situation as before. I want to be able to have
transaction handling code in one place - not in several objects that interact
by setting request variables etc.
Can you suggest a way to do this?
The only way I could see to do it is if RequestCycle.steps () was refactored to
throw any Exceptions with exception handling code (ie
IExceptionResponseStrategy.respond) in the calling method.
Then I could simply override this method to all intercept exceptions, commit
or rolllback transaction, and call super.steps() (or doSteps()) to resume
wickets normal error handling.
John
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
