On Tue, Mar 29, 2016 at 2:35 PM, Martin Grigorov <[email protected]> wrote:
> Yes, Jolira's code has been moved to Wicketstuff in early 6.x days. > > Stateless Ajax works for the simple cases but would fail for the use case > I've explained here: http://markmail.org/message/d7xuiao44owuyf56. > Although I guess the same is valid for non-Ajax stateless link too. > Someone just verified my theory: http://stackoverflow.com/q/36450085/497381 > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Tue, Mar 29, 2016 at 10:28 AM, Andrea Del Bene <[email protected]> > wrote: > >> I think this code has been already integrated into wicketstuff module >> stateless : >> https://github.com/wicketstuff/core/tree/master/stateless-parent >> On 29 Mar 2016 10:14, "Martijn Dashorst" <[email protected]> >> wrote: >> >> > All, >> > >> > I've done a small experiment with stateless ajax based on the code >> > from Jolira and ported it to wicket 7. >> > >> > It appears that stateless ajax actually works, and the code doesn't >> > look all that jarring to me. I understand that providing this >> > out-of-the-box, and as a default implementation is dangerous. >> > >> > >> > >> https://github.com/jolira/wicket-stateless/blob/master/stateless/src/main/java/com/google/code/joliratools/StatelessAjaxFormComponentUpdatingBehavior.java >> > >> > The only thing I had to fix was adding the following onBind method, >> > because Wicket's standard implementation doesn't perform this when >> > getStatelessHint() returns true: >> > >> > @Override >> > protected void onBind() >> > { >> > super.onBind(); >> > getFormComponent().getBehaviorId(this); >> > } >> > >> > The other snag I ran into was that the components you want to replace >> > need to have a static markupId (not generated by Wicket). >> > >> > Is this something we want to add to wicket proper? >> > >> > Martijn >> > >> > >> > -- >> > Become a Wicket expert, learn from the best: http://wicketinaction.com >> > >> > >
