ICEfaces
  1. ICEfaces
  2. ICE-10215

mobi:scan inside ui:repeat causes server error.

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Invalid
          • Affects Version/s: 4.0
          • Fix Version/s: EE-4.0.0.GA
          • Component/s: MOBI-Components
          • Labels:
            None
          • Environment:
            Tomcat 7, ICEfaces 4 trunk r42492, ios, android devices.
          • Assignee Priority:
            P2

            Description

            The first code scanned in the ui:repeat test causes the following server error. Subsequent scans do not produce the error. The application functions as expected.
            Sep 03, 2014 11:05:46 AM org.icefaces.impl.util.DOMUtils nodeDiff
            SEVERE: Diff propagated to root but no ID set [HTML: null]

            To reproduce
            Test app located at:
            http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/scan
            Navigate to mobi:scan inside ui:repeat.
            With server console open use one of the scan buttons.
            Observe the server error.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Arturo Zambrano added a comment -

              Marking as invalid because this wasn't really an issue with mobi:scan. The error message was displayed because the mobi:deviceResource component in the page was placed in the body, while it should always go in the head of a page.

              The mobi:deviceResource component renders some script, link and meta tags that should go in the head. It doesn't render a root container, and it doesn't render any client ids. Since, this tag was in the body and there was no root container and no client id, the DOMdiff was complaining about this, because it expects a client id on the root node of a component.

              The test page in the QA application was corrected and now has the mobi:deviceResource component in the head, and a note was added to the mobi:deviceResource TLD to specify that this component should go in the head section of a page.

              Show
              Arturo Zambrano added a comment - Marking as invalid because this wasn't really an issue with mobi:scan. The error message was displayed because the mobi:deviceResource component in the page was placed in the body, while it should always go in the head of a page. The mobi:deviceResource component renders some script, link and meta tags that should go in the head. It doesn't render a root container, and it doesn't render any client ids. Since, this tag was in the body and there was no root container and no client id, the DOMdiff was complaining about this, because it expects a client id on the root node of a component. The test page in the QA application was corrected and now has the mobi:deviceResource component in the head, and a note was added to the mobi:deviceResource TLD to specify that this component should go in the head section of a page.
              Hide
              Permalink
              Liana Munroe added a comment -

              Verified ICEfaces 4 trunk r43948

              Show
              Liana Munroe added a comment - Verified ICEfaces 4 trunk r43948

                People

                • Assignee:
                  Arturo Zambrano
                  Reporter:
                  Liana Munroe
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: