[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8687) JSF tooling adds an Faces Servlet declaration with no servlet mappings on project import
[
https://issues.jboss.org/browse/JBIDE-8687?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich commented on JBIDE-8687:
----------------------------------------------
Yes, web.xml is modified by WTP's JSFFacetInstallDelegate and there is no way to
configure him so that it would not do that. JBoss Tool's MavenJSFActivator configures
it this way
config.setProperty(IJSFFacetInstallDataModelProperties.SERVLET_NAME, "");
//$NON-NLS-1$
config.setProperty(IJSFFacetInstallDataModelProperties.SERVLET_URL_PATTERNS, new
String[0]);
obviously trying to make WTP do nothing with web descriptor. It works half way - servlet
mapping is not added, but servlet is added with the default name. And as it is worse in
that case to have no mapping at all, I suggest to set here *.xhtml mapping. Meanwhile, I
will report the problem to Eclipse Bugzilla.
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
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