<constant name="struts.serve.static" value="false" />
If you disable this feature, but use the
Custom Static Content Loaders
Static content is served by an implementation of
org.apache.struts2.dispatcher.StaticContentLoader. To write your own
StaticContentLoader and define a bean for the class:
<bean type="org.apache.struts2.dispatcher.StaticContentLoader" class="MyStaticContentLoader" name="myLoader" /> <constant name="struts.staticContentLoader" value="myLoader" />
Default Content Loader
Struts provides a default implementation of
StaticContentLoader which is
This loader will handle urls that start with “/static/”.
This content loader can serve static content from the classpath, so when writing a plugin, you can put a file inside your plugin’s jar like “/static/image/banner.jpg” and it will be served when the url “/static/image/banner.jpg” is requested.
This loader is not optimized to handle static content, and to improve performance, it is recommended that you extract your static content to the web application directory, and let the container handle them.
Preventing Struts from Handling a Request
If there is a request that Struts is handling as an action, and you wish to make Struts ignore it, you can do so by specifying a comma separated list of regular expressions like:
<constant name="struts.action.excludePattern" value="/some/content/.*?" />
These regular expression will be evaluated against the request’s URI (
HttpServletRequest.getRequestURI()), and if any
of them matches, then Struts will not handle the request.
To evaluate each pattern Pattern class from JDK will be used, you can find more about what kind of pattern you can use in the Pattern class JavaDoc.