Ted Husted wrote:
For a large, heavy-duty-input data-driven web application, I would recommend C.Do you have an example which uses multiple struts-config.xml and validator.xml files for dealing with "stories"?
C) [Conventional class] is NOT used, data form validation is defined within the
validation.xml and handled by struts, the Action class (or some
surrogate) then enforces all business rules.
I've had deep discussions with other large teams in similar circumstances, and the consensus has been that (C) is the most safe, sane, and simple route.
I would also recommend finely-grained DynaValidatorForms to ensure only the expected properties are captured and validated.
Nowadays, I also use finely-grained Struts configs, so that each "pageflow" or "story" is represented by its own struts-config.xml and validator.xml. This requires a strong naming convention to be sure the members of each config overlaps, but it makes it very easy to work with each use-case or story independently.
...
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
