[
https://issues.apache.org/jira/browse/TAP5-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAP5-966.
-------------------------------------
Resolution: Fixed
Fix Version/s: 5.2.0
> TapestryFilter should be able add additional modules to the Registry to
> accomidate different testing (or other) execution configurations
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-966
> URL: https://issues.apache.org/jira/browse/TAP5-966
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.2.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
