Hi, > how would I go about marking components as rendered?
Wicket marks components as they are rendered, this isn't something you need/should do.
Why aren't you just using a HiddenField? A quickstart would help to understand your problem, especially to compare it with Wicket 7.x.
Regards Sven Am 10.05.19 um 09:39 schrieb Ravi:
Hi all, I have a question regarding the rendering in Wicket 8.3.0. We have a Wicket 7.2.0 implementation of SecureForm for CSFR prevention similar to what shayy posted here http://apache-wicket.1842946.n4.nabble.com/Implementing-a-SecureForm-to-avoid-CSRF-attacks-td4666175.html Basically we programatically add the markup of a hidden input in onComponentTagBody( markup, tag) of the Form. This hidden input was added to the component tree in onInitialize. In onBeforeRender we mark the component as rendered. Worked fine so far. What seems to be happening is that onBeforeRender ist called in ComponentRenderingRequestHandler.beforeRender before component.renderPart ist called. RenderPart resets the renderedComponents in the Page - throwing away our hidden input that was added in onBeforeRender. Leaving us with an exception that ist thrown during Page.checkRendering. Is this the expected behavior and if so how would I go about marking components as rendered? Thanks for any hint, Ravi -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
