ICEfaces
  1. ICEfaces
  2. ICE-10812

include capability of ice:panelSeries into ace:panelStack and create UINamingContainerMeta so panelStack is naming container

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 4.1
    • Fix Version/s: EE-4.1.0.GA
    • Component/s: ACE-Components
    • Labels:
      None
    • Environment:
      jsf 2.2 ace
    • Assignee Priority:
      P1

      Description

      The ice:panelSeries component has some interesting features using class import com.icesoft.faces.context.DOMContext in the renderer class which directly manipulates the document model (attaching and removing nodes).
      The ace:panelStack could implement the new UISeriesMeta class and possibly use the handlers as well similar to this ComponentHandler (exposing the el for each var to the VariableMapper for each stackPane's handler to use).
      http://direct.massapi.com/source/jboss/41/37/413721292/nexus/content/repositories/root_repository/maven2/org/richfaces/ui/richfaces-ui/3.2.2.GA/richfaces-ui-3.2.2.GA-sources.jar/richfaces-ui-3.2.2.GA-sources.jar.unzip/org/richfaces/taglib/ComponentHandler.java.html
      ....
      or similar use of DOMContext could be considered (see which is more performant?).
      Note that ace:panelStack could also be a naming container, which is not included as a meta class in the generator (yet). This would allow use of id's for panelSTack within a c:forEach without getting errors for adding same component twice.

        Issue Links

          Activity

          Hide
          Judy Guglielmin added a comment -

          trying to place the var and value within the component and use it in a ComponentHandler does seem to work as the valueExpression for selectedId is not resolved in JSF until the component is created. A component that forces the values to be resolved for it's children (like c:forEach does at time of tree construction) would be preferred, but then a generic component could be used. (see ICE-10997)
          For now, UISeriesBaseMeta should be replaced with a simple NamingContainerMeta (see ICE-10996)

          Show
          Judy Guglielmin added a comment - trying to place the var and value within the component and use it in a ComponentHandler does seem to work as the valueExpression for selectedId is not resolved in JSF until the component is created. A component that forces the values to be resolved for it's children (like c:forEach does at time of tree construction) would be preferred, but then a generic component could be used. (see ICE-10997 ) For now, UISeriesBaseMeta should be replaced with a simple NamingContainerMeta (see ICE-10996 )
          Show
          Judy Guglielmin added a comment - replaced with http://jira.icesoft.org/browse/ICE-10996 and http://jira.icesoft.org/browse/ICE-10997

            People

            • Assignee:
              Judy Guglielmin
              Reporter:
              Judy Guglielmin
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: