Hi,
If the legacy app is again Servlet based then you can just add the new
Wicket app in the web.xml and serve anything that comes to /new/*, for
example.
If the app uses another technology then you will have to use shared DB
as you described.
On Tue, May 15, 2012 at 1:59 AM, kamiseq
the other technology is WebObjects and it uses its own server, I have
no idea if it can be easily ported to servlet container, anyway right
now it is not using one (as far I can tell).
Wicket stores only the last used page instance in the http session.
One instance!
And only if the page is
hej,
I need to handle 2 frameworks in the same time (one with legacy
application and wicket application that will handle pieces of old
functionality and new features - at least for some time until
everything is rewritten to wicket app) - maybe Im wrong here but this
means I need to share session
