Rendering performance

Hi, we have an issue with rendering performance and I wonder if there are any common misusages of wicket when it comes to this. When rendering a fully expanded tree with 160 top level nodes and mostly no subtrees (an expanded node is a forms with a bunch of labels and attributes) it takes about

Re: Rendering performance

Also it could be similar to https://issues.apache.org/jira/browse/WICKET-6177. There the user also has a lot of components in the tree and this takes time at page serialization time. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Jun 16, 2016 at 3:46 PM,

Re: stop wicket from rewriting references in my css file

Hi, If you don't add the CssUrlReplacer manually it is not active by default. If URLs are replaced into Reference URLs it might be a manually added CssUrlReplacer. If you don't want that some of the URLs are replaced you can consider to add them into a different CSS file and add the name of

Re: Generate css from less for package resources at runtime.

Hi Martin, many thanks for your efforts! Unfortunately this isn't a priority for our team at the moment. I'll get back to you if/when we dig deeper into this matter. Cheers Lasse 2016-06-08 22:04 GMT+02:00 Martin Grigorov : > HI Lasse, > > I've checked again Wicket

Re: Rendering performance

Hi Lasse, Which version of Wicket do you use ? I think you will have to use a profiler to see where the times is spent. It could be Wicket, but also it could be the application spending a lot of time while loading the data which should be rendered. Martin Grigorov Wicket Training and

Re: Rendering performance

Hi Martin, we use wicket 6.22. Doesn't the rendering take place when everything else is done? I.e the wicket components are already created and populated with data when the rendering phase starts. I guess I have to dig a bit deeper... anyway, thanks for your quick answers! Lasse 2016-06-16

Re: Rendering performance

Ok, that might have something to do with it! :-D Thanks! 2016-06-16 16:21 GMT+02:00 Martin Grigorov : > The models and data providers are asked for their data at render time. > Once the final data is available Wicket starts populating the HTML markup > with it. > > Martin

Re: Rendering performance

The models and data providers are asked for their data at render time. Once the final data is available Wicket starts populating the HTML markup with it. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Jun 16, 2016 at 4:17 PM, Lars Törner

Re: wicket-guice and recursive injection of non serializable JPA2 objects

Hi Dieter, Which version of wicket are you using? (I ask since I see you are using onBeforeRender() to initialize your components, while since wicket 1.5 there is onInitialize() for that in each component). For as far as I can see there are no references to your dao in the gist you provided;

Re: Implications of setRecreateBookmarkablePagesAfterExpiry()

Hi, I don't see how you could work around this. But I think we could remove the check at org.apache.wicket.Component#createRequestHandler(). I think it is fine to render urls with the page mount path in them. org.apache.wicket.core.request.mapper.AbstractBookmarkableMapper#processHybrid() is

Re: stop wicket from rewriting references in my css file

Ok it looks like it could be something like that. BUT,i've changed nothing from stock options. Could that be enabled by default in 6.22 . Other option of course are that it is because of something in pax wicket.. I'll go check. On Wed, Jun 15, 2016 at 1:15 PM, Bas Gooren wrote: >

Re: Problem migrating to Wicket 7

Hi Martin, I've added a much more simpler test application to show what's not working (see myproject2.zip below). On the first page you can see on the right side a TextComponent with a simple Behavior added to a Page. This Behavior adds some JavaScriptResourceReference (the jQuery function