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 <[email protected]> wrote: > 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 between those to frameworks. has anyone > done something like that. > > I thinking of using some key-value database that scales well or some > centralised custom rest service. > any thoughts on implementation provided that wicket stores a lot in > session, what about rendering to buffer and so on. Wicket stores only the last used page instance in the http session. One instance! And only if the page is stateful. With a custom IPageStore impl you can make this even 0, but then each Ajax request will load the page from the disk. > > pozdrawiam > Paweł Kamiński > > [email protected] > [email protected] > ______________________ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
