10 Replies Latest reply on Dec 1, 2008 10:08 AM by nbelaevski

IE7 client side response parsing error

jonmoores Nov 10, 2008 10:11 AM

I am using 3.2.2SR1 and see differences in the client response processing as well as its structure.

The examples I have are using Google Chrome versus IE7.

I found the problem because a commandLink -

<a4j:commandLink id="bestelLink" action="#{sessionBean.ShowBasket}" styleClass="link">
 <f:attribute name="article" value="#{item}"/>
 <h:graphicImage value="#{msg['image.shopping.cart']}" style="border: 0"/>
</a4j:commandLink>

was not navigating to the expected page in IE7 after clicking.

Initially the client side log shows that the DOCTYPE element is causing a problem:

debug[15:30:18,043]: exception during write page content undefined
error[15:30:18,062]: Error parsing responseXML Parsing Error: DTD is prohibited.
Location: Line Number 12, Column 11:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-----------^

After removing the doctype I get a problem concerning 'Whitespace is not allowed at this location':

error[15:33:47,046]: Error parsing responseXML Parsing Error: Whitespace is not allowed at this location.
Location: Line Number 39, Column 123:
<script type="text/javascript" language="Javascript">function dpf(f) {var adp = f.adp;if (adp != null) {for (var i = 0;i < adp.length;i++) {f.removeChild(adp);}}};function apf(f, pvp) {var adp = new Array();f.adp = adp;var i = 0;for (k in pvp) {var p = document.createElement("input");p.type = "hidden";p.name = k;p.value = pvp[k];f.appendChild(p);adp[i++] = p;}};function jsfcljs(f, pvp, t) {apf(f, pvp);var ft = f.target;if (t) {f.target = t;}f.submit();f.target = ft;dpf(f);};</script>
 ---------------------------------------------------------------------------------------------------------------------------^

I checked what happens in Chrome and that works ok although there are multiple ViewState elements created with the same id (I have two forms in the page).

Can anyone help me on resolving the XML parsing error?

Thanks
Jon

1. Re: IE7 client side response parsing error

nbelaevski Nov 10, 2008 11:06 PM (in response to jonmoores)
Hello,

Add this to web.xml as a workaround:
<context-param> <param-name>com.sun.faces.externalizeJavaScript</param-name> <param-value>true</param-value> </context-param>

Do you have special settings for parser in web.xml?
(like this:
<context-param> <param-name>org.ajax4jsf.xmlparser.ORDER</param-name> <param-value>NEKO, TIDY</param-value> </context-param>
)?
Actions
2. Re: IE7 client side response parsing error

jonmoores Nov 11, 2008 2:41 AM (in response to jonmoores)

Hi,

There's nothing extra in the web.xml.

Will try the workaround and let you know. Are there side effects to this param?

Thanks
Jon
Actions
3. Re: IE7 client side response parsing error

ronanker Nov 26, 2008 9:14 AM (in response to jonmoores)

i posted something in http://www.jboss.com/index.html?module=bb&op=viewtopic&t=141153 that can be a workaround for you...
Actions
4. Re: IE7 client side response parsing error

nbelaevski Nov 28, 2008 11:37 AM (in response to jonmoores)

Jon,

Different parsers have different performance. As renderers for some standard component do not output valid XHTML markup filter corrects it. The more performant filter corrects less errors. Select the one with that everything works.
Actions
5. Re: IE7 client side response parsing error

jonmoores Nov 30, 2008 11:59 AM (in response to jonmoores)

is there somewhere that tells me the list of possible parsers?
Actions
6. Re: IE7 client side response parsing error

ronanker Dec 1, 2008 3:53 AM (in response to jonmoores)

in my opinion Jon's issue isn't from server parser... it's a IE7 bug... IE7 try to parse content when using document.write or innerHtml... in some version of the dll that contains the parser there may be the bug...
but maybe i'm wrong, but i can reproduce this bug on some computer but not on others, 3 computers bug and 4 computers are ok for the exact equal ajax response, and i can't find what's different between them...
Actions
7. Re: IE7 client side response parsing error

ronanker Dec 1, 2008 3:57 AM (in response to jonmoores)

note that the error message you have in the a4j:log is client-side...
Actions
8. Re: IE7 client side response parsing error

ilya_shaikovsky Dec 1, 2008 8:28 AM (in response to jonmoores)

B.t.w. this also could be risen if you using navigation from a4j:control. Notice that navigation case should be redirect if navigation called by a4j control.
Actions
9. Re: IE7 client side response parsing error

jonmoores Dec 1, 2008 9:39 AM (in response to jonmoores)

that would be the case then...

I was not re-directing.
Thanks
Jon
Actions

10. Re: IE7 client side response parsing error

nbelaevski Dec 1, 2008 10:08 AM (in response to jonmoores)

Jon,

Available parsers are TIDY, NEKO and NONE.

Ronan,

I've already seen this problem:

error[15:33:47,046]: Error parsing responseXML Parsing Error: Whitespace is not allowed at this loca
tion.
Location: Line Number 39, Column 123:
<script type="text/javascript" language="Javascript">function dpf(f) {var adp = f.adp;if (adp != null) {for (var i = 0;i < adp.length;i++) {f.removeChild(adp
);}}};function apf(f, pvp) {var adp = new Array();f.adp = adp;var i = 0;for (k in pvp) {var p = docu
ment.createElement("input");p.type = "hidden";p.name = k;p.value = pvp[k];f.appendChild(p);adp[i++] = p;}};function jsfcljs(f, pvp, t) {apf(f, pv
p);var ft = f.target;if (t) {f.target = t;}f.submit();f.target = ft;dpf(f);};</script>
---------------------------------------------------------------------------------------------------
-----------------------^

. It is caused by XML parser failing to handle ' < ' in command link script, but not with the failing navigation.

Go to original post