[
https://issues.apache.org/jira/browse/JSPWIKI-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harry Metske resolved JSPWIKI-534.
----------------------------------
Resolution: Fixed
Fixed in 3.0.0-svn-118
> JSPWiki initalization fails the if the StripesFilter is not the first one to
> initialize
> ---------------------------------------------------------------------------------------
>
> Key: JSPWIKI-534
> URL: https://issues.apache.org/jira/browse/JSPWIKI-534
> Project: JSPWiki
> Issue Type: Bug
> Components: Core & storage, Servlet Container/Java compatibility
> Affects Versions: 3.0
> Environment: Jetty servlet container
> Reporter: Harry Metske
> Fix For: 3.0
>
>
> JSPWiki currently uses two servlet filters (WikiServletFilter and
> StripesFilter).
> For JSPWiki to init correctly the StripesFilter has to init first, if it's
> not the following error will occur:
> ERROR org.apache.wiki.WikiEngine - Failed to start managers.
> java.lang.IllegalStateException: WikiRuntimeConfiguration not found!
> The order of initialization of these filters is different per container
> (tomcat works, jetty doesn't).
> The JEE spec also does not guarantee the order of filter init'ing.
> It appears that in Jetty the order of init'ing is determined by the order the
> filters appear in the web.xml. So a very wrong workaround is to place
> WikiServletFilter after StripesFilter.
> Possible solution approach:
> Lazy init'ing of all filters except the StripesFilter
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
