Hello,
I have a form which requires some beans to be present in the request, in order to populate several dropdown boxes on the form. This occurs in an "edit" action which then returns an ActionForward to the form JSP. That much works fine. However, when the user tries to save their changes by calling the "save" action, automatic validation kicks in and the ActionServlet automagically forwards directly to the JSP listed in the "input" attribute of the "save" action. Because it goes directly to the JSP, no Action class gets a chance to populate these request beans, so the page pukes when it tries to render the dropdown boxes. Now, here's the rub. Changing the "input" attribute of the "save" action to point to the "edit" action ITSELF, instead of to the corresponding JSP page, DOES NOTHING. The ActionServlet still forwards control to the JSP directly, skipping the "edit" action. It never gets called! Is that weird or what? Now, I realize there's a simple fix to my original problem, which is that the dropdown boxes don't populate without the beans that drive them being in the request. I could put those beans in the application scope, for instance (ServletContext), and to tell you the truth, they should probably be there anyway. Nevertheless, this doesn't solve the general problem, which appears to be that the "input" attribute of an Action Mapping can't point to another Action. This seems so nonsensical, though, that I can hardly believe it. Can someone enlighten me on what's going on here? Thanks! Cheers, David David A. Ventimiglia Wells Fargo Private Client Services (415) 396-0414 (work)
