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

    IE7 client side response parsing error

    Jonathan Moores Newbie

      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