If you're using annotation-based results, and you extend ActionSupport, the
dummy action class is just a few lines -- it has no class body at all.
jk
On Fri, May 15, 2009 at 9:53 AM, Jim Collings wrote:
> I take it back. I only thought I had it figured out. I'll use the
> dummy action. I find it
I take it back. I only thought I had it figured out. I'll use the
dummy action. I find it distasteful but it seems the best way.
Jim C.
On Fri, May 15, 2009 at 9:07 AM, Jim Kiley wrote:
> What I've done in this situation is put in the dummy action. Inevitably I
> find myself needing some kind
What I've done in this situation is put in the dummy action. Inevitably I
find myself needing some kind of pre-processing before the JSP is loaded up
-- even when I don't initially believe that I will -- and the dummy action
is the right place for it.
jk
On Fri, May 15, 2009 at 7:40 AM, Jim Colli
Steve
-Original Message-
From: Jim Collings [mailto:jlistn...@gmail.com]
Sent: 15 May 2009 12:41
To: Struts Users Mailing List
Subject: Re: Problem dispatching in /content dir
Here's a bit of clarification:
page-one.jsp which is in /content
|
\-page-two <--Have to use this t
Here's a bit of clarification:
page-one.jsp which is in /content
|
\-page-two <--Have to use this to access page two because
it, also is in "/content". This means calling an empty "execute()".
|
\-page-two.jsp
|
\page-two <--Page tw
Jim,
The normal process is to call the action e.g.
Struts will then (eventually) call the actions execute () method. This
returns a string that is mapped to the correct jsp page using a file like
my-struts.xml. The mapping will look something like: -
/content/EverythingOK.jsp
6 matches
Mail list logo
