MyFaces CODI
  1. MyFaces CODI
  2. EXTCDI-171

allow custom parameters for view-configs

    Details

      Description

      it should be possible to extend a class annotated with @Page and annotate this class with @PageParameter.List({@PageParameter(key="customParam", value="#

      {customBean.value1}"), ...})
      if this class is used for navigation, codi should navigate to the page which is represented by the super-class (the class annotated with @Page) + all parameters should be added to the requested url.

      furthermore, it should be possible to use @PageParameter directly at the same view-config class which is annotated with @Page

      as an alternative it should be possible to annotate action methods with @PageParameter.
      e.g. @PageParameter(on = CustomPage.class, key="customParam", value="#{customBean.value1}

      ")
      ... this would be also an alternative to approach mentioned at the beginning. a central class could do all mappings. however, this would reduce the possibility to use existing IDE support and it isn't obvious at the first view that parameters will be added.

        Activity

        Gerhard Petracek created issue -
        Gerhard Petracek made changes -
        Field Original Value New Value
        Description it should be possible to extend a class annotated with @Page and annotate this class with @Parameter.List({@Parameter(key="customParam", value="#{customBean.value1}"), ...})
        if this class is used for navigation, codi should navigate to the page which is represented by the super-class (the class annotated with @Page) + all parameters should be added to the requested url.

        furthermore, it should be possible to use @Parameter directly at the same view-config class which is annotated with @Page
        it should be possible to extend a class annotated with @Page and annotate this class with @Parameter.List({@Parameter(key="customParam", value="#{customBean.value1}"), ...})
        if this class is used for navigation, codi should navigate to the page which is represented by the super-class (the class annotated with @Page) + all parameters should be added to the requested url.

        furthermore, it should be possible to use @Parameter directly at the same view-config class which is annotated with @Page

        as an alternative it should be possible to annotate action methods with @Parameter.
        e.g. @Parameter(on = CustomPage.class, key="customParam", value="#{customBean.value1}")
        ... this would be also an alternative to approach mentioned at the beginning. a central class could do all mappings. however, this would reduce the possibility to use existing IDE support and it isn't obvious at the first view that parameters will be added.
        Gerhard Petracek made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Show
        Gerhard Petracek added a comment - also see https://issues.apache.org/jira/browse/EXTCDI-216
        Gerhard Petracek made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Fix Version/s 1.0.2 [ 12317614 ]
        Resolution Fixed [ 1 ]
        Gerhard Petracek made changes -
        Issue Type Improvement [ 4 ] New Feature [ 2 ]
        Gerhard Petracek made changes -
        Description it should be possible to extend a class annotated with @Page and annotate this class with @Parameter.List({@Parameter(key="customParam", value="#{customBean.value1}"), ...})
        if this class is used for navigation, codi should navigate to the page which is represented by the super-class (the class annotated with @Page) + all parameters should be added to the requested url.

        furthermore, it should be possible to use @Parameter directly at the same view-config class which is annotated with @Page

        as an alternative it should be possible to annotate action methods with @Parameter.
        e.g. @Parameter(on = CustomPage.class, key="customParam", value="#{customBean.value1}")
        ... this would be also an alternative to approach mentioned at the beginning. a central class could do all mappings. however, this would reduce the possibility to use existing IDE support and it isn't obvious at the first view that parameters will be added.
        it should be possible to extend a class annotated with @Page and annotate this class with @PageParameter.List({@PageParameter(key="customParam", value="#{customBean.value1}"), ...})
        if this class is used for navigation, codi should navigate to the page which is represented by the super-class (the class annotated with @Page) + all parameters should be added to the requested url.

        furthermore, it should be possible to use @PageParameter directly at the same view-config class which is annotated with @Page

        as an alternative it should be possible to annotate action methods with @PageParameter.
        e.g. @PageParameter(on = CustomPage.class, key="customParam", value="#{customBean.value1}")
        ... this would be also an alternative to approach mentioned at the beginning. a central class could do all mappings. however, this would reduce the possibility to use existing IDE support and it isn't obvious at the first view that parameters will be added.
        Gerhard Petracek made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        77d 4h 11m 1 Gerhard Petracek 06/Jul/11 12:47
        In Progress In Progress Resolved Resolved
        67d 11h 9m 1 Gerhard Petracek 11/Sep/11 23:57
        Resolved Resolved Closed Closed
        85d 8h 8m 1 Gerhard Petracek 06/Dec/11 07:06

          People

          • Assignee:
            Gerhard Petracek
            Reporter:
            Gerhard Petracek
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development