Thanks! Now what might be better?  I have a legacy
application that has a "member" side and an "admin" side,
each with their own actions.

But many of the view pages are nearly identical.  The only
difference in most of the view pages is the form submit, e.g.:

<html:form action="/member/doThing">
<html:hidden property="state" value="go"/>
<html:hidden property="reservationId"/>
 ....

<html:form action="/admin/doThingForThem">
<html:hidden property="state" value="go"/>
<html:hidden property="reservationId"/>
 ....

It makes for a lot of duplicated view code, and messy
out-of-sync updates.


> Samere, Adam J" <[EMAIL PROTECTED]>
> The org.apache.struts.action.ActionMapping class provides access to this
> information. It is provided as the first parameter to the Action.execute
> method, and is also stored as a request attribute under the
> org.apache.struts.Globals.MAPPING_KEY key
> ("org.apache.struts.action.mapping.instance").
> 
> There may be a better way to do what you are attempting though...


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to