On Thu, May 28, 2009 at 4:01 PM, Christopher L Merrill <ch...@webperformance.com> wrote: > I've got a few questions that are somewhat general to web development, > but since we've chosen Wicket as one of our front-end frameworks, I > thought I would ask here first for pointers...especially where there > may be a "wicket way" of doing things that we need to be aware of. > > The system we're developing will have 2 UIs - a browser-based UI > developed in Wicket and an Eclipse-based rich-client app (Java). The > available functionality will be a little different in each but with a > good bit of overlap. There must be common authentication - a user > might use either UI or both at any given time. We'll likely be using > JAX-WS for communicating between the rich client and server. The server > will be Tomcat.
Why use JAX-WS if you don't have to? We use Spring remoting (with Spring security for common authentication/authorization) in our application and everything works just fine. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
