This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
An action mapping has a "roles" attrubute that you can use to assign which roles defined in the container have access to this action. So, as long as you use a separate action mapping when you intend to call either readAction or updateAction, you can define different roles for each. To me it would still make more sense to put each method in its own Action class since you have to define a separate mapping for each anyway. [ March 21, 2007: Message edited by: Merrill Higginson ]