Hi, I have noticed that when deploying a Stripes WAR file that has, for reasons of application separation, got its own jar load, the boot up process for the server involves lots of stack traces, along the lines of "Unable to examine ...
sure, but have you set the "ActionResolver.UrlFilters" initparam in your web.xml? It's used to restrict the classpath entries that are searched for ActionBeans. Without this setting, Stripes searches all URLs in the web app classpath, which can be a lot (and trying to inspect some entries ...
I just googled this, http://mc4j.org/confluence/display/stripes/ConfigurationReference#ConfigurationReferenceActionResolver, which neatly describes how to speed up startup by doing as you suggest
Mail Thread
