ICEfaces
  1. ICEfaces
  2. ICE-6652

IE 7 displaying Message: 'isXMLResponse' is undefined

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.0.1
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      IE 7 , icefaces 2

      Description

      The jsf pages we developed works perfectly fine on Firefox and IE 8 but it seems IE 7 has an issue with finding 'isXMLResponse'
      The following message is displayed.

      Message: 'isXMLResponse' is undefined
      Line: 2047
      Char: 17
      Code: 0

        Issue Links

          Activity

          Hide
          Hari Pulijala added a comment -

          xhtml is attached where we are getting this error. This xhtml is included in another xhtml which has ice:form and ice:panelGroup in it.
          This is very severe for us as most of the end users are expected to use the IE 7.

          Show
          Hari Pulijala added a comment - xhtml is attached where we are getting this error. This xhtml is included in another xhtml which has ice:form and ice:panelGroup in it. This is very severe for us as most of the end users are expected to use the IE 7.
          Hide
          Ken Fyten added a comment -

          Looking at this, it might be related to the use of the Alloy JSF components on the page.

          However, we would require a succinct executable test case (and source), preferably a .war file ready for deployment to Tomcat 6, with as much content removed as possible but that still shows the problem, in order to review this further.

          Show
          Ken Fyten added a comment - Looking at this, it might be related to the use of the Alloy JSF components on the page. However, we would require a succinct executable test case (and source), preferably a .war file ready for deployment to Tomcat 6, with as much content removed as possible but that still shows the problem, in order to review this further.
          Hide
          Deryk Sinotte added a comment -

          It's possible that the issue with "isXmlContent" not being defined has been fixed as per ICE-6411. I recommend testing your application against the latest icefaces2/trunk to verify.

          Show
          Deryk Sinotte added a comment - It's possible that the issue with "isXmlContent" not being defined has been fixed as per ICE-6411 . I recommend testing your application against the latest icefaces2/trunk to verify.
          Hide
          Hari Pulijala added a comment -

          Hi,

          I tired with icefaces-2.0.1-24185.jar and icefaces-compat-2.0.1-24185.jar which i believe are the latest from trunk.
          I am getting the following exception and the portlet itself is not able to deploy:
          Caused by: java.lang.ClassNotFoundException: org.icefaces.impl.context.DOMPartialViewContext

          thanks,
          hari

          Show
          Hari Pulijala added a comment - Hi, I tired with icefaces-2.0.1-24185.jar and icefaces-compat-2.0.1-24185.jar which i believe are the latest from trunk. I am getting the following exception and the portlet itself is not able to deploy: Caused by: java.lang.ClassNotFoundException: org.icefaces.impl.context.DOMPartialViewContext thanks, hari
          Hide
          Yannick Majoros added a comment - - edited

          I had the same error message in Firefox console ('isXMLResponse' is undefined ). It prevented an error to be displayed when there was an exception. Actually, I was trying to redirect to an error page when there was whatever exception, but it didn't work until I corrected this in bride.js (line 2047):

          broadcast(serverErrorListeners, [ e.responseCode, e.responseText, isXMLResponse ? xmlContent : null]);

          was changed to this:

          broadcast(serverErrorListeners, [ e.responseCode, e.responseText, e.responseXML ]);

          I'm not sure my patch is perfect, but I'm almost sure it just couldn't work as it was written. I guess it was dependent on old code that was removed.

          Anyway, it now seems to work.

          Hope this will be fixed in trunk...

          Show
          Yannick Majoros added a comment - - edited I had the same error message in Firefox console ('isXMLResponse' is undefined ). It prevented an error to be displayed when there was an exception. Actually, I was trying to redirect to an error page when there was whatever exception, but it didn't work until I corrected this in bride.js (line 2047): broadcast(serverErrorListeners, [ e.responseCode, e.responseText, isXMLResponse ? xmlContent : null]); was changed to this: broadcast(serverErrorListeners, [ e.responseCode, e.responseText, e.responseXML ]); I'm not sure my patch is perfect, but I'm almost sure it just couldn't work as it was written. I guess it was dependent on old code that was removed. Anyway, it now seems to work. Hope this will be fixed in trunk...
          Hide
          Yannick Majoros added a comment -

          Looks quite similar to ICE-6546...

          Show
          Yannick Majoros added a comment - Looks quite similar to ICE-6546 ...
          Hide
          Luiz Abrahao added a comment -

          Just to let you know. I'm getting the same error on Firefox 4 and Safari 5.0.4 on a Mac OS X 10.6.6.

          That is happening when there is something wrong with my XHML page.

          ICEfaces 2.0.0
          Build number: 4
          Revision: 23692

          Show
          Luiz Abrahao added a comment - Just to let you know. I'm getting the same error on Firefox 4 and Safari 5.0.4 on a Mac OS X 10.6.6. That is happening when there is something wrong with my XHML page. ICEfaces 2.0.0 Build number: 4 Revision: 23692

            People

            • Assignee:
              Unassigned
              Reporter:
              Hari Pulijala
            • Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: