Tapestry 5
  1. Tapestry 5
  2. TAP5-966

TapestryFilter should be able add additional modules to the Registry to accomidate different testing (or other) execution configurations

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 5.2.0
    • Fix Version/s: 5.2.0
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      Frequently when integration testing an application, it is desirable to re-configure some parts of it (i.e., special symbol defaults, new service overrides, special service configurations), which currently is ad-hoc or otherwise awkward.

      How about if there was a special JVM system property: tapestry.execution-mode. This would be a comma-seperated list of mode names. For each one, the T5 filter would check for a <init-parameter> named "tapestry.foo-modules" (where "foo" is a mode name) and add those to the Registry. The default value for execution-mode would be "production" ... thus you could easily have certain module classes loaded for normal production and a different set loaded for integration testing.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development