because you needed to first make youre own SessionFactory then youre own Session then youre own RequestCycle factory and then last
the RequestCycle itself. that where 4 classes and 5 methods just to do one thing (implement one method)
Now in the 1.2 stream it is easier to create a RequestCycle so we could think of moving it.
johan
On 12/19/05, John Patterson <[EMAIL PROTECTED]> wrote:
On Monday 19 Dec 2005 09:33, Eelco Hillenius wrote:
> No need for that anymore, it's 'fixed' now (though I don't entirely
> agree as I stated in another thread).
>
Thanks guys! I have used WebWork previously and this is my first Wicket
project. I think it is bloody brilliant. I am really looking forward to
zero state support. By the way, I also feel that the RequestCycle would be
the natural place to have such an handle exception listener.
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
