On Fri, 14 Mar 2003 11:03:58 -0600 Dan Allen <[EMAIL PROTECTED]> wrote:
> If I were to use DispatchAction for CRUD actions, there is a problem > I run into. Assuming that most of the actions will need a form, but > struts-config reads > > <action > path="/Member" > name="memberForm" > type="net.creativerge.struts.action.MemberDispatchAction" > validate="true"> > <forward name="confirmation" path="/confirmation.jsp"/> > </action> > > However, how would the delete work? Surely you won't want to > validate the delete form as it would make little sense. In short, > my issue is that some actions will want to validate and others will > not. Also, what if the permissions change per action? Am I > bringing up things that point me back to seperate actions? You don't have to use the same mapping to go to one DispatchAction. (I should probably show that in another lesson so it's not confusing). In other words you could have a delete button call the action: /deleteMember and still use in your mapping: type="net.creativerge.struts.action.MemberDispatchAction" So you end up with different action mappings but still get to incorporate more than one event in the actual mapping. -- Rick Reumann --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
