DeltaSpike
  1. DeltaSpike
  2. DELTASPIKE-390

optional custom ConfigPreProcessor for @ViewMetaData

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.4
    • Fix Version/s: 0.5
    • Component/s: JSF-Module
    • Labels:
      None

      Description

      @ViewMetaData#preProcessor is predefined per view-meta-data.
      it should be possible to replace the default implementations globally (via the config mechanism of deltaspike).

      example:
      org.apache.deltaspike.jsf.api.config.view.View$ViewConfigPreProcessor=org.custom.CustomViewConfigPreProcessor
      -> org.custom.CustomViewConfigPreProcessor should be used instead of org.apache.deltaspike.jsf.api.config.view.View$ViewConfigPreProcessor

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        10m 56s 1 Gerhard Petracek 07/Jul/13 14:07
        Resolved Resolved Closed Closed
        255d 17h 37m 1 Gerhard Petracek 20/Mar/14 07:44
        Gerhard Petracek made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Gerhard Petracek made changes -
        Summary optional custom ConfigPreProcessor optional custom ConfigPreProcessor for @ViewMetaData
        Gerhard Petracek made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Gerhard Petracek made changes -
        Assignee Gerhard Petracek [ gpetracek ]
        Gerhard Petracek made changes -
        Field Original Value New Value
        Description @ViewMetaData#preProcessor is predefined per view-meta-data.
        it should be possible to replace the default implementations globally.
        @ViewMetaData#preProcessor is predefined per view-meta-data.
        it should be possible to replace the default implementations globally (via the config mechanism of deltaspike).

        example:
        org.apache.deltaspike.jsf.api.config.view.View$ViewConfigPreProcessor=org.custom.CustomViewConfigPreProcessor
        -> org.custom.CustomViewConfigPreProcessor should be used instead of org.apache.deltaspike.jsf.api.config.view.View$ViewConfigPreProcessor
        Gerhard Petracek created issue -

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development