I like the idea of having my startup context separated from the bulk context, but something does not seem correct and looking at how long it takes for splash screen to come up ....
Anyway, I am refereing to the following code in ApplicationLauncher:
This code still loads both of the context at the same time. Granted in launchMyRichClient() only startup used but I would think if you have a long enough descriptor you would still see a pause before splash comes up (and that is exactly what I see with petclinic).Code:public ApplicationLauncher(String startupContextPath, String[] rootContextPath) { Assert.notEmpty(rootContextPath, "One or more root rich client application context paths must be provided"); this.startupContext = loadStartupContext(startupContextPath); this.rootApplicationContext = loadRootApplicationContext(rootContextPath); launchMyRichClient(); }
should launch be broken up on two launch with startup context and launch with root context to speed thing up?
It would be nice to provide visual feedback on startup so splash could be a progress monitor
Thanks,
Alex.


Reply With Quote