Hello,
one way to solve it is not to duplicate code in different Action classes,
but have many ActionMapping entries in your struts-config.xml file.
This way you keep the navigational part of your application away from Action
classes, but still avoid code duplication in Actions.
HTH,
--
Hi Brian,
Why not use different named forwards for the action and access each one from
the action with a:
{
...
return (mapping.findForward(page1/page2/page3));
}
In s-c:
action path=/myAction
type=FQ Class
name=bean
...
forward name=page1 path=/page1.jsp/
forward name=page2
To: Struts Users Mailing List
Subject: RE: Design Question - same action, many jsps/views
Hi Brian,
Why not use different named forwards for the action and access each one
from
the action with a:
{
...
return (mapping.findForward(page1/page2/page3));
}
In s-c:
action path=/myAction
type=FQ Class
Users Mailing List [EMAIL PROTECTED]
To: 'Struts Users Mailing List' [EMAIL PROTECTED]
Subject: RE: Design Question - same action, many jsps/views
Date: Mon, 28 Jul 2003 16:26:52 +0100
Hi Hue,
That's definitely one way to go, but the disadvantage that
I see of using this way is that you presumably have
you don't have it: http://www.livinglogic.de/Struts
Hue.
-Original Message-
From: Brian McSweeney [mailto:[EMAIL PROTECTED]
Sent: 28 July 2003 16:27
To: 'Struts Users Mailing List'
Subject: RE: Design Question - same action, many jsps/views
Hi Hue,
That's definitely one way
be worth a look,
too?
URL in case you don't have it: http://www.livinglogic.de/Struts
Hue.
-Original Message-
From: Brian McSweeney [mailto:[EMAIL PROTECTED]
Sent: 28 July 2003 16:27
To: 'Struts Users Mailing List'
Subject: RE: Design Question - same action, many jsps/views
Hi Hue
6 matches
Mail list logo
