Wicket 8 rendering of components

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

Re: Possible memory leak with Tomcat?

Thanks Sven. On Thu, May 9, 2019 at 8:24 PM Sven Meier wrote: > Hi, > > we've had two fixed related to page stores (WICKET-6457, WICKET-6564) so > please upgrade to 7.13.0 first. > > Have fun > Sven > > > Am 09.05.19 um 21:10 schrieb Wayne W: > > Hi, > > > > I've take a memory dump of one of

Re: Wicket 8 rendering of components

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

Control how and where the Bootstrap css resources are included in the page

Hi, I would like to know whether there is a way to decide where to place the Bootstrap css resources in the element. I'm asking this because I have a "BookmarkablePageLink" element on page A and, when you click it, it redirects to page B. Now on B I see all my custom css resource files that

Re: Control how and where the Bootstrap css resources are included in the page

Hi! To ensure your resources render *after* bootstrap, you need to make them dependent on the bootstrap css resource. You can override HeaderItem#getDependencies() in your custom CssHeaderItem, and add the bootstrap css resource to its list of dependencies. Met vriendelijke groet, Kind regards,