First, thanks for the help. Item 1 implemented via @SpringBean(name =
"blah"). ;)
On May 16, 2008, at 3:31 PM, Igor Vaynberg wrote:
there are basically two things that you need no matter what web
framework you are integrating with:
1) a way to lookup your dao singleton
wicket-ioc allows you to quickly build an annotation based injection
2) a way to scope the entity manager to request
you need this so that lazy loading works. you are already doing this
with a threadlocal already, the only thing you need to do is to wire
in that closeEntityManager() call.
you can either do this with a servlet filter that sits around the
wicket filter, or you can hook into wicket's requestcycle and do it
from there. there are really no advantages either way.
I'll ask for help with this bit on the Spring list to help avoid
clutter here.
The filter route sounds like want I want, as I would prefer to keep as
much of the "bookkeeping" as possible out of the application logic.
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
