Thanks for your help. I havnt tried this yet becaouse this involves some refactoring and I wanted to be sure that I'll choose correct solution.
Daniel Stoch-2 wrote: > > No, I don't say you need OSGi container, but in more complex > environments it may be helpful. > Of course you can, as you wrote, map WicketFilter multiple times and > this should work - why you didn't try this yet? :) > > -- > Daniel > > On Mon, Feb 2, 2009 at 12:03 PM, Daniel Lipski > <[email protected]> wrote: >> >> Do I really need OSGi container ?(OSGi is great idea, but I would like to >> keep this simple) >> Why I cant just map WicketFilter multiple times ? I would like to stay >> with >> one war deployed on Tomcat container. >> >> >> Daniel Stoch-2 wrote: >>> >>> Maybe you should look at OSGi? Then each of your application can be >>> defined inside a different bundle and runs on the same JVM. We are >>> using such approach in our environment and it works very well. A small >>> downside of such solution is that you have to learn what is it and how >>> to use OSGi (unless you already know it ;)). >>> >>> -- >>> Daniel > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://www.nabble.com/Multi-module-applications-in-Wicket-tp21774998p21788104.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
