[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8687) JSF tooling adds an Faces Servlet declaration with no servlet mappings on project import

[Dan Allen (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-8687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596618#comment-12596618 ] 

Dan Allen commented on JBIDE-8687:
----------------------------------

I would really prefer that the web.xml not be changed. We don't need the Faces Servlet in EE 6 so there is no need for the JSF configurator to change anything if the schema is 3.0. However, I would not be opposed if you added a complete Faces Servlet configuration. My main concern is that the configurator is breaking the application so that it won't deploy, so people think that the projects they import are broken. (Case in point, generate a project using http://tinyurl.com/gojavaee and JBoss Tools breaks the project).

> 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