The GenericFilter should be called after that the request context has been properly set --------------------------------------------------------------------------------------- Key: GTNPORTAL-1339 URL: https://jira.jboss.org/browse/GTNPORTAL-1339 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA, 3.0.0-GA Reporter: Nicolas Filotto In GateIn, we have an HttpFilter called GenericFilter that is used to allow integrators/customers/partners/dev teams to add new Filters in the "portal" web application without modifying the web.xml file. This GenericFilter relies on an ExtendedFilter that allows to define filters thanks to a component-plugin. Few days ago, I wanted to create a dedicated filter that allows us to override a jsp file in portal.war from the war of my extension, this prototype allows me to realized that the GenericFilter is called too quickly in the filter chain. It should be called at least after that the entire context has been set such as the current PortalContainer and so on (i.e. after SetCurrentIdentityFilter and ThreadLocalSessionProviderInitializedFilter). Ideally it should be called in last position. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira