[
https://issues.jboss.org/browse/JBIDE-8687?page=com.atlassian.jira.plugin...
]
Snjezana Peco resolved JBIDE-8687.
----------------------------------
Resolution: Done
I can't reproduce the issue either using the JBT 3.3.0 trunk or JBT 3.2 stable
branch.
The Maven JSF Configurator isn't called if a project already contains the JSF facet.
If you want to reproduce the problem using an existing project, you need to do the
following:
- check the "web.xml for JSF 2.0 facet" preference
- right click the project and call Properties>Project Facets
- delete the JSF facet
- right-click the project and call Maven>Update Project Configuration
or
- create a new project using the jboss-jee6-webapp archetype
- check the "web.xml for JSF 2.0 facet" preference
- import the project using the Import>Existing Maven Projects action
If after these steps the web.xml is still unchanged (no servlet definition is added to
it), please reopen this jira.
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: Snjezana Peco
Priority: Blocker
Fix For: 3.3.0.M1, 3.2.1.M1
Attachments: jbide-8687.png
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