> I have a large application written in WebWork, Spring and iBATIS. After
> having started working with Wicket it really pains me that I have to
> continue developing with WebWork, so I want to start migrating this
> application on a page-by-page basis :)
>
> I'm thinking I'd add a filter for wicket with a "/w" filter-mapping, and
> migrate one page after another.
>
> The WebWork session holds information about currently logged in user,
> currently selected customer etc, and I need a way to sync this with a
> Wicket session. I could ofcourse add this information to the url
> everytime I hit a Wicket-page, but that seems really messy.
I don't know how WebWork stores it's sessions, but I imagine they do
that just in the HttpSession, right? So all you need then is knowing
what attribute (keys) are being used. You could write a custom Wicket
session that proxies these, such as:
class MySession extends WebSession {
...
public User getUser() {
return
(User)MyRequestCycle.get().getHttpSession().getAttribute("_webwork_user");
}
Note that for the other way around, you can use WicketSessionFilter.
Eelco
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
