I did exactly this for an old application. I wrote all the new code
in Wicket and just shared the log-in details from the session. They
would log in using wicket and the WW pages would check for the user
object in the HttpSession. Was very painless.
On 3 Nov 2007, at 16:49, Edvin Syse wrote:
Hi,
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.
Any suggestions?
Sincerely,
Edvin Syse
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
