[
https://issues.jboss.org/browse/JBIDE-8687?page=com.atlassian.jira.plugin...
]
Dan Allen commented on JBIDE-8687:
----------------------------------
The reason I am not opposed to adding a complete Faces Servlet configuration is because
the application server provided configuration does not block *.xhtml files. So we would
effectively be fixing that problem by updating the web.xml.
I'm also concerned that the comments that were in the web.xml get stripped out.
Comments should be preserved, but that is probably an upstream issue.
JSF tooling adds an Faces Servlet declaration with no servlet
mappings on project import
----------------------------------------------------------------------------------------
Key: JBIDE-8687
URL:
https://issues.jboss.org/browse/JBIDE-8687
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF, UpStream
Affects Versions: 3.2.0.Final
Reporter: Dan Allen
Assignee: Viacheslav Kabanovich
Priority: Blocker
Fix For: 3.2.1, 3.3.0.M1
When importing a Java EE 6 webapp that contains a faces-config.xml descriptor, the JSF
tooling unnecessarily adds a Faces Servlet declaration to the web.xml. The Faces Servlet
is not required in Java EE 6 (at least on JBoss AS and GlassFish). What's worse, the
Servlet is added with no mappings, so it completely breaks JSF.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira