Hi,
well, Ajax4jsf should normally work without problems in combination
with myfaces.
The only thing i know of which you have to be aware of, is that the
special Ajax4jsf-filter has
to be placed before any other filters in your web.xml.
Try to leave out this <dispatcher> stuff, don`t know if it is really required.
What are the other problems?
cheers,
Gerald
On 10/7/06, Stephen Osella <[EMAIL PROTECTED]> wrote:
Does ajax4jsf work with myfaces? If so, does anyone have a link or some
idea as to how to configure it to work? I am getting *lots* of errors.
For one, getting the following error with respect to the web.xml
configuration:
21:22:26,897 - WARN
org.apache.myfaces.shared_impl.webapp.webxml.WebXmlParser - Ignored element
'dispatcher' as child of 'filter-mapping'.
21:22:26,897 - WARN
org.apache.myfaces.shared_impl.webapp.webxml.WebXmlParser - Ignored element
'dispatcher' as child of 'filter-mapping'.
21:22:26,897 - WARN
org.apache.myfaces.shared_impl.webapp.webxml.WebXmlParser - Ignored element
'dispatcher' as child of 'filter-mapping'.
when setting up web.xml as:
<filter>
<display-name>Ajax4jsf Filter</display-name>
<filter-name>ajax4jsf</filter-name>
<filter-class>org.ajax4jsf.Filter</filter-class>
</filter>
<filter-mapping>
<filter-name>ajax4jsf</filter-name>
<servlet-name>Faces Servlet</servlet-name>
<dispatcher>REQUEST</dispatcher>
<dispatcher>FORWARD</dispatcher>
<dispatcher>INCLUDE</dispatcher>
</filter-mapping>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
