Hi, On Tue, Feb 7, 2012 at 1:02 PM, toytown <[email protected]> wrote: > Hi igor, > > i certainly do agree that being stateful Wicket can do complex stuff. > However, you have to consider the fact that sometimes it is necessary to > become stateless (especially in public facing website) where I need the > users to be able to bookmark the page . > i do not see whats wrong in integrating some stateless behaviours, links > like those in Jorilla Project into the wicket core so that users can get the > best of both world from wicket framework.
I think the problem to integrate such behaviors is that someone will face problems like the one I described earlier in this thread and file a ticket which we wont be able to solve. When I upgraded Jolira's stateless project to 1.5 I asked the original author whether it is OK to put it in WicketStuff project so it will be released for each version of Wicket but he preferred to keep it in his Github repo. I think it works fine with 1.5.4 but since it is not part of our release cycle it may get broken at some point ... :-/ > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Stateless-and-Ajax-tp4344007p4364341.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
