Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.9.3
    • Component/s: None
    • Labels:
      None

      Description

      basically codi configuration is based on cdi mechanisms.
      however, there are artifacts which have to be configured before cdi is up and running.
      instead of hardcoding config names,... it should be handled via implementations of ConfiguredValueResolver.
      that also allows to introduce custom config approaches e.g. for the project stage.

      via the existing @InvocationOrder annotation it should be possible to specify the order and via the ClassDeactivator approach it should be possible to deactivate existing implementations of ConfiguredValueResolver.

      optionally it should be possible to aggregate implementations (if it makes sense for the specific artifact)

      without custom implementations it should be possible to configure artifacts via:

      • system property
      • service loader
      • jndi

        Issue Links

          Activity

          Gerhard Petracek created issue -
          Gerhard Petracek made changes -
          Field Original Value New Value
          Status Open [ 1 ] Resolved [ 5 ]
          Fix Version/s 0.9.3 [ 12316038 ]
          Resolution Fixed [ 1 ]
          Gerhard Petracek made changes -
          Link This issue relates to EXTCDI-121 [ EXTCDI-121 ]
          Gerhard Petracek made changes -
          Assignee Gerhard Petracek [ gpetracek ]
          Gerhard Petracek made changes -
          Status Resolved [ 5 ] Closed [ 6 ]

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development