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 Collings <jlistn...@gmail.com> wrote: > 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 two action "page-two!dosomething" > > Now I could put in a dummy action that just forwards to "page-two.jsp" > but why? It seems like there should be a better way. > > > Jim C. > > On Fri, May 15, 2009 at 7:16 AM, Jim Collings <jlistn...@gmail.com> wrote: > > > > So I have a jsp that needs to submit to another jsp. Both are in > /content. When I use file-name.jsp I get 404. When I use file-name, I get > the action that file-name.jsp submits to. > > > > Any ideas on how I can work around this? > > > > Jim C. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org > > -- Jim Kiley Senior Technical Consultant | Summa [p] 412.258.3346 http://www.summa-tech.com
