so a patch is not necessary, we already fully support what you want. what would be nice instead is a unit test that makes sure the exception does in fact get through. that way we can make sure we do not break this behaviour with future refactorings.
-Igor
On 12/16/05, John Patterson <[EMAIL PROTECTED]> wrote:
On Friday 16 Dec 2005 14:27, Igor Vaynberg wrote:
> if you really want to you are free to cutomize any piece of request cycle
> processing you want, in this case take a look at
> IExceptionResponseStrategy.
I can't find this interface... but for the reasons of simplicity and keeping
all transaction handling logic in once place it would be much preferable to
simply be able to use a try-catch block around the code.
Using this interface would mean that hibernate sessions are commited and
closed in one place and rolled back in another with some kind of ad-hoc
signalling between them (eg through a request parameter).
Very messy when such a simple alternative is available. Can I supply a patch
to be considered?
Thanks,
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
