[TAP5-966] TapestryFilter should be able add additional modules to the Registry to accomidate different testing (or other) execution configurations

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.2.0
• Fix Version/s: 5.2.0
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 31/Dec/09 22:57
• Updated: 05/Jan/10 18:39
• Resolved: 05/Jan/10 18:39

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.