Date: 2004-03-02T15:23:49 Editor: ArchimedesTrajano <[EMAIL PROTECTED]> Wiki: Jakarta Cactus Wiki Page: Cactus2Proposal URL: http://wiki.apache.org/jakarta-cactus/Cactus2Proposal
no comment Change Log: ------------------------------------------------------------------------------ @@ -39,3 +39,5 @@ Both have pros and cons. However, the biggest drawback for the first solution (CactusTestSetup) is that it does not offer a solution on the server side (there is no JUnit Test Runner on the server side). Thus for the server side, there is only a single generic solution I can imagine: using a generic Aspects to intercept Cactus user-defined Aspects and using a static variable to remember if the Cactus system has already been initialized. Note that using Java system properties would be enough for passing configuration data but not enough for a proper initialization phase (which is needed for example if we're using a component-based approach like PicoContainer). The other problem with the TestSetup solution is that it is more complex for Cactus users who need to wrap all tests in a test suite. Thus, I think the Aspect initialization is probably the best route. Any other idea? -- VincentMassol + +Cactus2AlternatePropsoal -- ArchimedesTrajano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
