org.apache.myfaces.shared_impl.webapp.webxml.WebXmlParser readFilterMapping
> > WARNING: Ignored element 'servlet-name' as child of 'filter-mapping'.
> >
> > <filter-mapping>
> > <filter-name>AdfFacesFilter</filter-name>
> > <servlet-name>FacesServlet</servlet-name>
> > </filter-mapping>
> > <filter-mapping>
> > <filter-name>MyFacesExtensionsFilter</filter-name>
> > <servlet-name>FacesServlet</servlet-name>
> > </filter-mapping>
> >
> > Perhaps because my filter-mappings are defined before my servlets?
On 4/14/06, Adam Winer <[EMAIL PROTECTED]> wrote:
You're seeing a bug
> in the MyFaces's WebXmlParser code - it only understands
> url-pattern. I suspect that this means you need to change
> the ExtensionsFilter mapping from servlet-name to url-pattern,
> which will probably fix up #1, but you should also file a bug against
> MyFaces to support servlet-name mappings for ExtensionsFilter.
Unless something has regressed recently, MyFaces most certainly
supports servlet-name. I use it almost exclusively in my web.xml
file, and it's the recommended way to install the Extensions filter on
our web site.
<!-- extension mapping for adding <script/>, <link/>, and other
resource tags to JSF-pages -->
<filter-mapping>
<filter-name>MyFacesExtensionsFilter</filter-name>
<!-- servlet-name must match the name of your
javax.faces.webapp.FacesServlet entry -->
<servlet-name>FacesServlet</servlet-name>
</filter-mapping>
