On Monday, September 26, 2011 8:39 PM, "koha...@gmail.com" <koha...@gmail.com> wrote: > We have to have the > Servlets in front due to current connection from IIS and Apache.
That doesn't make any sense. For IIS and Apache it really doesn't matter at all. > Here is what the architecture of my implementation looks like: > > Dispatcher Servlet > (awaiting incoming httpservletRequest) > | > Wicket Components > > On the Application Service layer, I have > > EJB Beans > > And then on the Data Layer I have > JPA/Entity > > My question is what should I be concerned about in accessing Wicket > Components from the Servlets since the URL would be connecting directly > to servlets. I would never advice to do it this way. If you want to keep your application in a request-based dispatcher kind of architecture, than don't use wicket. If your reason for moving to wicket is to have better maintainable software, then by all means, don't rebuild everything exactly the same in wicket. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
