RE: [tomahawk] oamSubmitForm causes parse error

2008-02-01 Thread Michael Heinen
. I think there were also some other threads in the past regarding the missing CDATA statements. Michael From: Martin Marinschek [mailto:[EMAIL PROTECTED] Sent: Freitag, 1. Februar 2008 00:10 To: MyFaces Discussion Subject: Re: [tomahawk] oamSubmitForm causes parse error No ideas

RE: [tomahawk] oamSubmitForm causes parse error

2008-02-01 Thread Simon Kitching
also some other threads in the past regarding the missing CDATA statements. Michael From: Martin Marinschek [mailto:[EMAIL PROTECTED] Sent: Freitag, 1. Februar 2008 00:10 To: MyFaces Discussion Subject: Re: [tomahawk] oamSubmitForm causes parse error No ideas

RE: [tomahawk] oamSubmitForm causes parse error

2008-02-01 Thread Michael Heinen
is org.apache.myfaces.shared_tomahawk.renderkit.html.HtmlRendererUtils. I'll vote for TOMAHAWK-722 Michael -Original Message- From: Simon Kitching [mailto:[EMAIL PROTECTED] Sent: Freitag, 1. Februar 2008 12:06 To: MyFaces Discussion Subject: RE: [tomahawk] oamSubmitForm causes parse error Hi Michael, Are you generating

[tomahawk] oamSubmitForm causes parse error

2008-01-31 Thread Michael Heinen
I am using myFaces in combination with ajax4jsf (or richfaces) and tried to use the Nekko Parser (or Neko?) in the richfaces filter to achieve better performance. Some tomahawk javascript code makes now trouble: The parser says: error[18:11:35,796]: Parse Error: XML Parsing Error: A name was

Re: [tomahawk] oamSubmitForm causes parse error

2008-01-31 Thread Martin Marinschek
No ideas, no patches. Is it the which is not liked by the parser? regards, Martin On Thu, Jan 31, 2008 at 6:33 PM, Michael Heinen [EMAIL PROTECTED] wrote: I am using myFaces in combination with ajax4jsf (or richfaces) and tried to use the Nekko Parser (or Neko?) in the richfaces filter to