[
https://issues.apache.org/jira/browse/MYFACES-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Korherr resolved MYFACES-2579.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0-beta-3
Assignee: Jakob Korherr
This works now :)
If you run MyFaces 2.0 in a Servlet 3.0 container, you don't add an entry for
the FacesServlet in your web.xml and you have either classes in your webapp
that are annotated with and of the MyFaces 2.0 annotations (e.g. @ManagedBean)
or if the faces-config.xml file exists, the container will add the FacesServlet
automatically and you will get this log entry:
INFO: Added FacesServlet with mappings /faces/*, *.jsf and *.faces
Tested on GlassFish v3 and it worked just perfect!
> Support the dynamic adding of servlets and servlet-mappings on Servlet API
> 3.0 to make web.xml entries for Faces Servlet not mandatory
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MYFACES-2579
> URL: https://issues.apache.org/jira/browse/MYFACES-2579
> Project: MyFaces Core
> Issue Type: New Feature
> Affects Versions: 2.0.0-beta-3
> Environment: Environment with Servlet API 3.0 available.
> Reporter: Jakob Korherr
> Assignee: Jakob Korherr
> Fix For: 2.0.0-beta-3
>
> Attachments: core-pom.patch, myfaces-impl-pom.patch
>
>
> This would be a really cool new feature, because we could use the new Servlet
> API to add the entries for Faces Servlet dynamically at startup and so the
> user does not have to configure it anymore in web.xml.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
