Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.0
    • Fix Version/s: None
    • Component/s: Components/Renderers
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: Macintosh

    • Issuezilla Id:
      641
    • Status Whiteboard:
      Hide

      cat2 javadoc size_medium importance_medium

      Show
      cat2 javadoc size_medium importance_medium

      Description

      Consider:

      Using Page:
      -----------------------
      <h:form id="f">
      <cc:compcomp id="outer" attr="foo"/>
      </h:form>

      compcomp.xhtml
      ----------------------
      <cc:implementation>
      #

      {component.clientId} Do something fancy here<br />
      <c:if test="#{cc.attrs.attr != 'stop'}">
      <test:compcomp id="inner" attr="stop">
      <h:outputText value="#{cc.clientId}
      #{cc.attrs.attr}"/><br />
      </test:compcomp>
      </c:if>
      <cc:insertChildren />
      #{component.clientId}

      Do even more fancy stuff here... <br />
      </cc:implementation>

      Should this be allowed?

      In the example above, <h:outputText value="#

      {cc.clientId}

      #

      {cc.attrs.attr}

      "/>
      will display the inner composite client ID and the value 'stop', when the actual
      intent was to display the outer id and the value 'foo'.

      The updated #

      {cc} resolution semantics require that #{cc}

      expressions resolve
      the composite component relative to the template they were defined in, however,
      with the current API, we have no way to disambiguate which component to use.

        Activity

        Hide
        rogerk added a comment -

        triage

        Show
        rogerk added a comment - triage
        Hide
        rogerk added a comment -

        triage

        Show
        rogerk added a comment - triage
        Hide
        rogerk added a comment -

        triage

        Show
        rogerk added a comment - triage
        Hide
        Ed Burns added a comment -

        Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.

        Show
        Ed Burns added a comment - Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.
        Hide
        Manfred Riem added a comment -

        Setting priority to Minor

        Show
        Manfred Riem added a comment - Setting priority to Minor

          People

          • Assignee:
            Unassigned
            Reporter:
            Ryan Lubke
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: