Hi, I want to know the opinion of the another developers of this list with your experience in modelling the struts Action classes. What's the ideal point of Action classes granularity?
One approach is building one Action for each Use Case. Example: NewUserAction, EditUserAction, ListUserAction (for dealing with creation, listing and update of user data in an application). I like this approach because of the direct mapping from the use case models to java classes. Another approach is to build one class for each "operation": UserAction, for example. This action will be more complex than in the first approach, but we will have fewer action classes. What is your experience in this topic? Any other approaches for dealing with this? Thanks in advance, Victolla --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
