From: Thom Burnett [mailto:[EMAIL PROTECTED]
> My question is, what's the recommended practice. Is it considered best
> to keep different actions for each major purpose or to have one Action
> (controller) sorting and dispatching incoming requests.
There's already a mechanism in place for sorting
Thom Burnett wrote:
My question is, what's the recommended practice. Is it considered best to
keep different actions for each major purpose or to have one Action
(controller) sorting and dispatching incoming requests.
There is controller already ;-) ActionServlet is a controller which
dispatches
What is the general approach in creating action classes for Struts.
At the moment, any given project that I work on seems to have pretty close
to one new Action class for each page.
If the page is at all complicated, has it's own form or data, it seems to
need a separate Action.execute(). In fact
3 matches
Mail list logo
