type:
>
>
>
> or on indivdual actions using the className
>
>
> Niall
>
> ----- Original Message -
> From: "Riyad Kalla" <[EMAIL PROTECTED]>
> To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
> Sent: Friday, A
our actions by
setting the type:
or on indivdual actions using the className
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Friday, April 23, 2004 11:08 PM
Subject: Re: Benefits of LookupDispatchAction without parameter nonsense
> Hrrm.. I just found
OTECTED]
Voice: (310) 470-1257
Fax:(310) 362-8454
Sun Microsystems iForce Partner
-Original Message-
From: Joe Hertz [mailto:[EMAIL PROTECTED]
Sent: Friday, April 23, 2004 3:11 PM
To: 'Struts Users Mailing List'
Subject: RE: Benefits of LookupDispatchAction without para
1.2 Gives you MappingDispatchActions
The ActionMapping Path's will be different, but you can still
consolidate everything into one class.
/ObjectSave -> ActionClass.save()
/ObjectEdit -> ActionClass.edit()
You do this with the parameter attribute for each individual mapping.
You use the name o
Hrrm.. I just found MappingDispatchAction and that seems to be exactly what I
was looking for... has anyone used this class?
On Friday 23 April 2004 03:00 pm, Riyad Kalla wrote:
> Hey guys,
> After playing with the LookupDispatchAction most of the day and converting
> over some existing functiona
5 matches
Mail list logo