[
https://jira.jboss.org/jira/browse/RF-6034?page=com.atlassian.jira.plugin...
]
Alexander Smirnov commented on RF-6034:
---------------------------------------
The Ajax4jsf filter is configured in the AbstractFacesTest#setupFacesServlet() method.
To create test for Jboss Seam that method should be overwritten:
/**
* This template method called from {@link #setUp()} to create {@link FacesServlet}
instance.
* The default implementation also tests presense of the "org.ajax4jsf.Filter"
class.
* If this class is avalable, these instance appended to the Faces Servlet call chain.
* Default mapping to the FacesServlet instance is "*.jsf"
*/
protected void setupFacesServlet() {
ServletContainer facesServletContainer = new ServletContainer("*.jsf",
new FacesServlet());
facesServletContainer.setName("Faces Servlet");
FilterContainer filterContainer = new FilterContainer(new SeamFilter(),
facesServletContainer);
filterContainer.setName("seam");
facesServer.addServlet(filterContainer);
facesServer.addWebListener(new SeamListener());
}
The stage server does not parse web.xml hense all additional init parameters, filters and
listeners should be prepared in the code. This is not a limitation but test-related
feature; that behavior allows to test a same application with different configurations.
Provide JSF-Test support for Seam Apps
--------------------------------------
Key: RF-6034
URL:
https://jira.jboss.org/jira/browse/RF-6034
Project: RichFaces
Issue Type: Feature Request
Affects Versions: 3.3.0
Reporter: John Gilbert
Assignee: Alexander Smirnov
Fix For: 3.3.1
JSF-Test doesn't appear to like the fact that Seam initializes the a4j filter instead
of the web.xml.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira