tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Created: (TAP5-966) TapestryFilter should support a test mode (from a JVM system proprerty) and an init parameter to specify additional module classes when in test mode
Date Thu, 31 Dec 2009 22:58:29 GMT
TapestryFilter should support a test mode (from a JVM system proprerty) and an init parameter
to specify additional module classes when in test mode
----------------------------------------------------------------------------------------------------------------------------------------------------

                 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
            Priority: Minor


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.

If the T5 filter included an init-param "tapestry.test-modules" as a comma-separated list
of module classes to load (in addition to the default) that would be great.

Possibly this could be generalized to a "run-mode" that could be "test" or "integration" (or
any arbitrary string) and Tapestry would include "tapestry.xyz-modules" if it exists as an
init param.  The default would be "production" which would allow for some large scale swapping
out of production modules vs. test modules.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message