If you are using Struts 1.2.9, then lookup EventActionDispatcher.
-Original Message-
From: Scott Van Wart [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 21, 2006 1:39 PM
To: Struts Users Mailing List
Subject: Re: Struts Design question
Monkeyden wrote:
> If your implementation
Monkeyden wrote:
If your implementation is similar to what Scott has mentioned (i.e.
different operations on the same type of object), then I consider this a
classic example of a DispatchAction, where type of business entity
doesn't
change...just the selected operation on the business entity, th
If your implementation is similar to what Scott has mentioned (i.e.
different operations on the same type of object), then I consider this a
classic example of a DispatchAction, where type of business entity doesn't
change...just the selected operation on the business entity, thus it makes
sense t
Kavita Mehta wrote:
Hi,
I have a form which has 3 submit buttons .
which is a gud ides ...
1) having seperate 3 action classes for each
2) having a single action class which manages the submit action based
on the button which has called this action class.
It's up to you ;). I typically divide
It sounds like WildCard mappings (since Struts 1.2) might help. You
would probably only need one set of mappings for any number of
catagories.
You would probably only need one ActionForm too. If some of the
categories don't use some of the properties, then they just travel
null. Just give the base
5 matches
Mail list logo
