Thanks Howard. Works and goes a long way! Saves about 70% of the start-up
time.
Szemere
This was noted by a couple of my clients during training.
Andy's solution is OK, except its hard to load a page sometimes when
there's no active request.
You can force the Hibernate to initialize early, which is 9 of your 10 seconds:
public void contributeRegistryStartup(OrderedConfiguration
con
Thanks for the suggestion, thought I couldn't get that quite to work. I'm on
Tapestry 5.0.11 and got the following. Upgraded to 5.0.15 to see if that
made any difference (a better error message ensues), but it hasn't done the
trick.
5.0.11
[INFO] Starting jetty 6.1.7 ...
2008-11-10 21:24:14.344::I
This is me thinking out loud, so this might not work at all because i
haven't tried it. But here's what my first go at this would be.
In the application module:
public static void contributeRegistryStartup(OrderedConfiguration
configuration, @Inject @Value("${tapestry.start-page-name}"
+1
Szemere Szemere schrieb:
Is there an easy way to have Tapestry auto-load or auto-request the start
page when the core Tapestry servlet loads up?
The first page to load when we restart Tapestry takes over 10seconds (mostly
because of Hibernate and number of linked pages), which we only get
Is there an easy way to have Tapestry auto-load or auto-request the start
page when the core Tapestry servlet loads up?
The first page to load when we restart Tapestry takes over 10seconds (mostly
because of Hibernate and number of linked pages), which we only get to when
making the first request
