Tom,
You can safely ignore the warning about the dispatcher element. There
was a problem with WebXmlParser not recognizing this tag in MyFaces
version 1.1.4 but it should be resolved in new releases (see
https://issues.apache.org/jira/browse/MYFACES-1415 for more information).
Regards,
Gert Vanthienen
[EMAIL PROTECTED]
Tom Innes wrote:
Thanks Mario,
Your suggestions where bang on. Though I find the results somewhat
surprising.
Using jsp:forward with the dispatcher filter mappings yields this in the log
09:10:39,493 WARN [WebXmlParser] Ignored element 'dispatcher' as child of
'filter-mapping'.
For each mapping. Yet it works. I find this surprising because the warning
seems to indicate that I should have no change in behavior.
Removing the dispatcher filter mappings and replacing the jsp:forward with
<%@ page session="false" contentType="text/html;charset=utf-8"%>
<%
response.sendRedirect("conversation/pageConversation.xhtml");
%>
Works.
Thank you very much for your help.
Tom
PS
I look forward to playing with the conversation components as they are
exactly what I need for my application.
-----Original Message-----
From: Mario Ivankovits [mailto:[EMAIL PROTECTED]
Sent: October 21, 2006 1:57 AM
To: Tom Innes
Subject: Re: Conversation - Filter Exception
Hi Tom!
If you get a chance could you look at this and see what the issue is. I
tried sending this to the newsgroup but it bounced.
Thanks for the sample. I'll give it a go during the weekend, though, I
had a quick look at the setup and I think it has something to do with
the jsp:forward thing.
Try avoiding the jsp:forward or add the following two lines to your
filter-mappings
<dispatcher>REQUEST</dispatcher>
<dispatcher>FORWARD</dispatcher>
Just a quick guess ... ;-)
Hope it helps.
Ciao,
Mario
