I'm looking for a good anti-pattern to my suggestion. Is there
a reasonable use-case where using UndoableEdits would not yield the
correct/expected behavior?
My hope is that there is none and we can all agree to move
forward on this issue. Remember, if no UndoableEdit is registered for a
rendering operation then hitting Back yields a "page is stale" message.
It seems quite intuitive to me. :|
Gili
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
