We have a new wicket app that is waiting until the third page in our app before it loads a WHOLE LOT of properties stuff. I turned to debug and got literally thousands of these:
[3/22/17 13:56:49:282 EDT] 00000142 SystemOut O DEBUG ResourceStreamLocator Attempting to locate resource 'mypackage/ocp/modules/contact/ContactPage_Cp12_en_US.properties' using finder'[classpath]' [3/22/17 13:56:49:283 EDT] 00000142 SystemOut O DEBUG ResourceStreamLocator Attempting to locate resource 'mypackage/ocp/modules/contact/ContactPage_Cp12_en_US.properties' using finder'[webapppath: /]' [3/22/17 13:56:49:290 EDT] 00000142 SystemOut O DEBUG ResourceStreamLocator Attempting to locate resource 'mypackage/ocp/modules/contact/ContactPage_Cp12_en_US.properties' using finder'[classpath: META-INF/resources/]' [3/22/17 13:56:49:291 EDT] 00000142 SystemOut O DEBUG ResourceStreamLocator Attempting to locate resource 'mypackage/ocp/modules/contact/ContactPage_Cp12_en_US.properties' using finder'[webapppath: /OnlineClaimsPetitions/]' It's taking 3.5-5 seconds once per startup. That doesn't sound bad, but it happens on an ajax event that ought to be lightweight and kind of creates a bad user experience for that first person in. I'd like to preload or do this step on startup if possible. How can I make that happen? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-properties-file-load-at-startup-tp4677396.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
