Hi all, I've done quite a bit of reading and prototyping, and it seems that Wicket is going to be our best bet for building our application. I have a few questions.
I found a good thread on nabble here about serialization and stateless pages. The wiki has some documentation here https://cwiki.apache.org/WICKET/stateless-pages.html How easy is it to build stateless pages? We're looking at building components of our site, then assembling them together via a central look and feel. Our system will run on a distributed cluster, so we can't guarantee sticky sessions. We could serialize sessions to Cassandra, but I'd prefer to avoid session serialization as much as possible. We'll be using the open auth 1.0a authentication framework. Has anyone used Wicket with oAuth/spring security before? Our design person will be building all the mockups using Html and jQuery. I've found this plugin. http://code.google.com/p/wiquery/wiki/QuickStart Has anyone implemented this? We've decided jQuery will be our main JS library, but I want to avoid any pitfalls of integrating it incorrectly from the start. I would also like Spring and my business tier to perform most of the validation. We'll be exposing a lot of our services as REST services, so I want the business tier to validate the input is correct. Are there any tutorials/documentation on how to link these two into the wicket validation framework? Thanks in advance for answering all the noob questions. Todd --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
