Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: EE-2.0.0.Beta1
    • Fix Version/s: EE-3.0.0.GA
    • Component/s: Facelet Components
    • Labels:
      None
    • Environment:
      JSF2/ICEfaces2

      Description

      The richTabs.xhtml composite component uses a <f:setPropertyActionListener/> but JSF 2.0 does not like how it is used. In the current implementation we assume that setCurrentTab(tab) is called but after reading the tld doc for <f:setProeprtyActionListener /> I don't think is being used correctly and likely can be refactored to work.

        Activity

        Patrick Corless created issue -
        Patrick Corless made changes -
        Field Original Value New Value
        Assignee Brad Kroeger [ brad.kroeger ] Patrick Corless [ patrick.corless ]
        Patrick Corless made changes -
        Salesforce Case []
        Fix Version/s EE-2.0.0.Beta1 [ 10254 ]
        Hide
        Patrick Corless added a comment -

        This doesn't effect the compat cc components. Targeting beta2

        Show
        Patrick Corless added a comment - This doesn't effect the compat cc components. Targeting beta2
        Patrick Corless made changes -
        Salesforce Case []
        Fix Version/s EE-2.0.0.Beta2 [ 10256 ]
        Fix Version/s EE-2.0.0.Beta1 [ 10254 ]
        Ken Fyten made changes -
        Fix Version/s EE-2.0.0.Beta1 [ 10254 ]
        Fix Version/s EE-2.0.0 [ 10256 ]
        Hide
        Patrick Corless added a comment -

        The component also used dynamic ui:includes which could also being causing an issue with jsf 2.0. Regardless the problem reported here is only with the JSF 2 refactored components.

        At this point it's not clear if we will take another shot at porting the cc's to jsf2.0 but I'll move it 2.1 so we don't loose the issue.

        Show
        Patrick Corless added a comment - The component also used dynamic ui:includes which could also being causing an issue with jsf 2.0. Regardless the problem reported here is only with the JSF 2 refactored components. At this point it's not clear if we will take another shot at porting the cc's to jsf2.0 but I'll move it 2.1 so we don't loose the issue.
        Patrick Corless made changes -
        Salesforce Case []
        Fix Version/s EE-2.1.0 [ 10261 ]
        Fix Version/s EE-2.0.0.Beta1 [ 10254 ]
        Hide
        Philip Breau added a comment -

        working as expected now

        Show
        Philip Breau added a comment - working as expected now
        Philip Breau made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Ken Fyten made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Patrick Corless
            Reporter:
            Patrick Corless
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: