You could instead use a OpenSessionInViewFilter (which you can
blatently copy from Spring) that opens a hibernate session for you and
you can use that in both your wicket app and legacy app.
Martijn
On 12/22/06, ChuckDeal [EMAIL PROTECTED] wrote:
I have a legacy app that I am replacing with
Chuck's using extended sessions, so using that filter for the Wicket
side wouldn't be an option. But I also don't think that wrapping a
Wicket RequestCycle around a servlet request is a good idea (if it's
even possible).
Instead, I would use a filter for the legacy stuff only. You can still
tie
I have a legacy app that I am replacing with Wicket. It has to be done over
time, so I can't do a wholesale rewrite of the app. I have Wicket as the
main framework and my legacy, homemade framework will be the secondary.
The few Wicket/Databinder pages that I have work pretty well. My legacy
Here is the Filter that I implemented (
http://www.nabble.com/file/5085/AIMSFilter.java AIMSFilter.java ). It works
for me, for now... I still don't fully understand what I have done, I think
understanding will come with some more experimentation and exploration.
I don't even know if this is
