ICEfaces
  1. ICEfaces
  2. ICE-2878

<jsp:root> causes javascript error

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Invalid
          • Affects Version/s: 1.7DR#3, 1.7Beta1
          • Fix Version/s: 1.7
          • Component/s: Framework
          • Labels:
            None
          • Environment:
            Any
          • Affects:
            Compatibility/Configuration
          • Workaround Exists:
            Yes
          • Workaround Description:
            Hide
            It's not really valid to have JSP directives in a Facelets page. There are two main techniques for using a <jsp:root> tag, for IDE code completion, such that Facelets will strip it out. Failing to use these techniques isn't really supported. In fact, we have ICE-1279 so as to warn developers of their mistake of having a JSP directive remain in the component tree. This particular Javascript failure is not really the issue. The solution is to do one of the following:

            A. Put the <jsp:root> tag outside of a <ui:composition> tag, so that it will simply be discarded.

            B. Use <jsp:root jsfc="f:view">, so that the <jsp:root> tag will become an <f:view> tag.
            Show
            It's not really valid to have JSP directives in a Facelets page. There are two main techniques for using a <jsp:root> tag, for IDE code completion, such that Facelets will strip it out. Failing to use these techniques isn't really supported. In fact, we have ICE-1279 so as to warn developers of their mistake of having a JSP directive remain in the component tree. This particular Javascript failure is not really the issue. The solution is to do one of the following: A. Put the <jsp:root> tag outside of a <ui:composition> tag, so that it will simply be discarded. B. Use <jsp:root jsfc="f:view">, so that the <jsp:root> tag will become an <f:view> tag.

            Description

            Using <jsp:root> tag on a page causes a javascript error "uncaught exception: couldn't find container for property: bridge".

            This issue did not occur in 1.7DR#2 and below.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Jacky Lee added a comment -

              attached testcase

              Show
              Jacky Lee added a comment - attached testcase
              Hide
              Permalink
              Mircea Toma added a comment -

              It looks like com.sun.facelets.compiler.StartElementInstruction is trying to insert the jsp:root tag directly into the HTML markup (using the ResponseWriter).

              Show
              Mircea Toma added a comment - It looks like com.sun.facelets.compiler.StartElementInstruction is trying to insert the jsp:root tag directly into the HTML markup (using the ResponseWriter).
              Hide
              Permalink
              Mark Collette added a comment -

              It's not really valid to have JSP directives in a Facelets page. There are two main techniques for using a <jsp:root> tag, for IDE code completion, such that Facelets will strip it out. Failing to use these techniques isn't really supported. In fact, we have ICE-1279 so as to warn developers of their mistake of having a JSP directive remain in the component tree. This particular Javascript failure is not really the issue. The solution is to do one of the following:

              A. Put the <jsp:root> tag outside of a <ui:composition> tag, so that it will simply be discarded.

              B. Use <jsp:root jsfc="f:view">, so that the <jsp:root> tag will become an <f:view> tag.

              Show
              Mark Collette added a comment - It's not really valid to have JSP directives in a Facelets page. There are two main techniques for using a <jsp:root> tag, for IDE code completion, such that Facelets will strip it out. Failing to use these techniques isn't really supported. In fact, we have ICE-1279 so as to warn developers of their mistake of having a JSP directive remain in the component tree. This particular Javascript failure is not really the issue. The solution is to do one of the following: A. Put the <jsp:root> tag outside of a <ui:composition> tag, so that it will simply be discarded. B. Use <jsp:root jsfc="f:view">, so that the <jsp:root> tag will become an <f:view> tag.

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Jacky Lee
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: