On 11/08/2003 16:45 "Mainguy, Mike" wrote:
I have a quick question. In what manner is everyone mapping their actions?
Do you have multiple actions per action class or just one action per action class.
We're working on a demo application and extension framework, but are rather undecided on whether to make each possible atomic action it's own class, or provide a mechanism to embed (sub)actions in the form data to ease the proliferation of classes and mappings that the other way would seem to cause.
I.E. do you have
ProjectCreate.class
ProjectRead.class
ProjectUpdate.class
ProjectDelete.class [snip]
I tend to make my action classes process several related actions but it's probably more important to apply a consistent approach than to chose one or the other.
--
Paul Thomas
+------------------------------+---------------------------------------------+
| Thomas Micro Systems Limited | Software Solutions for the Smaller Business |
| Computer Consultants | http://www.thomas-micro-systems-ltd.co.uk |
+------------------------------+---------------------------------------------+
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
