Right, right, my bad. But then you should create three different webmodules for a single application, that's why wicket would be loaded 3 times only for this separation.. It's just unneccesary resource usage IMHO.
2009-12-28 16:30 keltezéssel, Pieter Degraeuwe írta: > Hmm, that's not correct. Different frontend apps should use the same EJB's. > In that case, It's not so ugly anymore in my opinion. (I don't want to > advocate the use of EJB's though..) > > 2009/12/28 Major Péter <majorpe...@sch.bme.hu> > >> Hi, >> >> 2009-12-28 15:57 keltezéssel, Jim Pinkham írta: >>> OK, but could you deploy multiple copies of the same app to different >> root >>> contexts - that would give you the info you want in each URL and thus be >>> able to do different home/error pages with some config along with each >> copy >>> of the app. Seems worth exploring whether your Silos might divide well >> in >>> this manner, maybe with a bit of work, but probably more likely to happen >>> than what it seems like you are looking for, which doesn't sound (just >> one >>> casual observer's option) broadly applicable enough to warrant framework >>> inclusion. >> >> this wouldn't work easily, because for example when you have EJBs in >> your project, you can't deploy the same app to different contextroots, >> because the EJBs JNDI name is already bounded, so this way you would >> have to run your slightly different apps on different appservers too, >> and that's just ugly. I think Martin has a point there, maybe Wicket >> should support this use-case. >> >> Regards, >> Peter >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
