[jboss-jira] [JBoss JIRA] Commented: (JBAS-8521) Filters not registered when applications start up
[
https://jira.jboss.org/browse/JBAS-8521?page=com.atlassian.jira.plugin.sy...
]
Shelly McGowan commented on JBAS-8521:
--------------------------------------
I noted that this was filed against M5 but thought I'd try on the latest to see where
we're at. One thing I did note from your logs is:
09:02:31,455 INFO [javax.enterprise.resource.webcontainer.jsf.config] Initializing Mojarra
2.0.4 (SNAPSHOT 20100826) for context '/pretty-prime-test'
6.0.0.M5 had Mojarra 2.0.2-FCS
From my log above, jbossas/trunk currently has Mojarra 2.0.3
(JBAS-7739)
19:53:57,328 INFO [javax.enterprise.resource.webcontainer.jsf.config]
Initializing Mojarra 2.0.3 (SNAPSHOT 20100726) for context '/mateo'
Stan will look into this further.
Filters not registered when applications start up
-------------------------------------------------
Key: JBAS-8521
URL: https://jira.jboss.org/browse/JBAS-8521
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Java EE APIs
Affects Versions: 6.0.0.M5
Environment: JBoss AS M5 - Ubuntu 10.10
Reporter: Lincoln Baxter III
Assignee: Stan Silvert
Attachments: pretty-prime-test.tar.gz, prettyfaces-test.tar
It seems like custom filters are not being booted when JBoss starts applications - place
a breakpoint in PrettyFilter.init(ServletContext context) and it will never fire. Nor is
the filter ever invoked on web-requests.
The attached application can be used to reproduce this on M5. This works on Glassfish.
--
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