Details

    • Type: Sub-task Sub-task
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.0
    • Fix Version/s: None
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      421
    • Status Whiteboard:
      Hide

      cat2 frame size_large importance_large draft

      Show
      cat2 frame size_large importance_large draft

      Description

      Currently, all configuration informations have to be available on framework
      startup. This prevents the development of modular JSF applications with OSGi,
      JPF or any other module platform, where modules of the application are installed
      or replaced at runtime.

      Suppose you have a JSF application distributed over several OSGi bundles, each
      of which contains a logical unit of the application. As long as all bundles are
      available on startup and never change at runtime, there is no problem, for the
      configuration can be stored in a META-INF/faces-config.xml file in each bundle
      and a proper TCCL strategy will find the config files of all bundles at startup.

      However in OSGi (and in similar platforms) bundles can change over time.
      Contained new or changed views will be (re-)read by the view-handler and thus
      are "dynamic" out of the box. It would be nice if elements like components,
      validators, converters and navigation rules could be registered when starting
      the bundle and unregistered when it is stopped.

      It won't make much difference whether configuration at runtime is done using
      config files or an API. Maybe by using config files the feature can be
      implemented without making it to the specification. In any case no dependency to
      any concrete module platform would be added.

      As OSGi gets more and more popular on the server side and frameworks like
      Eclipse RAP make heavy use of it today, this could become more important in the
      future. Corresponding features recently made its way into the Servlet 3.0 early
      draft too (JSR315, section 4.4 and 8).

        Activity

        Hide
        Ed Burns added a comment -

        These are targeted at 2.1.

        Show
        Ed Burns added a comment - These are targeted at 2.1.
        Hide
        Ed Burns added a comment -

        triage

        Show
        Ed Burns 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:
            maestrobirero2
          • Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated: