ICEfaces
  1. ICEfaces
  2. ICE-6644

Javascript error, caused after executing an ajax request

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Won't Fix
          • Affects Version/s: 2.0.0
          • Fix Version/s: None
          • Component/s: ICE-Components
          • Labels:
            None
          • Environment:
            JBoss 5.1
            JSF 2.1
            Portlet faces bridge 2.0.0BETA4

            Description

            After clicking a tab it loads but a JavaScript-Error occurs:
            "detect(parents(element), function (e) {return e.configuration;}) is null"
            This is probably due the div-container of the portlet does not contain the "configuration-object" after being replaced by the new DOM-content.
            You probably will have to adjust all the javascript code to work on portlets, it seems the configuration does not get written to the portlet div-container after the successful ajax-request.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Neil Griffin added a comment -

              Ken: Hold off on trying to reproduce this one. I've reproduced it and I think I might know what the problem is.

              Show
              Neil Griffin added a comment - Ken: Hold off on trying to reproduce this one. I've reproduced it and I think I might know what the problem is.
              Hide
              Permalink
              Neil Griffin added a comment -

              @Christian: It turns out that this is not a bug in ICEfaces. I'm fairly certain that the JavaScript issue was caused by the patch you made in your local copy of the bridge source code for http://jira.portletfaces.org/browse/BRIDGE-180

              I had to provide an alternative patch for BRIDGE-180 – please see my comments there. For this issue, I'm going to resolve it as WONTFIX.

              Show
              Neil Griffin added a comment - @Christian: It turns out that this is not a bug in ICEfaces. I'm fairly certain that the JavaScript issue was caused by the patch you made in your local copy of the bridge source code for http://jira.portletfaces.org/browse/BRIDGE-180 I had to provide an alternative patch for BRIDGE-180 – please see my comments there. For this issue, I'm going to resolve it as WONTFIX.

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Christian Heike
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: