> In Struts, although you aren't FORCED to, what you GENERALLY do is > create > three different Action classes like addItemAction, removeItemAction > and > totalPriceAction, and each is called in response to a form > submission.
Most (if not all) the Actions in my current application extend LookupDispatchAction in order to help group common methods together. If I was doing a ShoppingCart, I would have a single ShoppingCartAction that contained add(), update(), delete(), as well as any private helper methods. I agree with you that most people do generally split that up into three seperate classes. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
