Hi all, First of all, I feel that this forum is great, and the technology being developed by the Wicket folks is simply amazing. I am trying to pitch Wicket to my organization that has a Spring mvc implementation in place (yet the web 2.0 requirements are far beyond what it can handle - hence the need for re-investigation). The insistence of Spring designers on stateless-ness has made this idea of transitioning to a session-heavy framework a rather tough one. I'm therefore curious to know about the timeline for Wicket 2.0, which I believe will support stateless components? Can you guys suggest some interim strategies (mitigating factors) in the meanwhile?
thanks jaf -- View this message in context: http://www.nabble.com/Wiket-2.0-time-frame-tp16992791p16992791.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]
