Hi! Well, by "presentational side" I meant the side of the server logic where you have already determined what view to pass to the client.
In the setup I have, every action has its own JSP for rendering itself, but sometimes I have a need to call a different action instead of rendering that corresponding JSP. Currently this is done via redirects, which as far as I have read is nothing unusual. What I would like to do now is replace the redirect with a direct call to the following action. Is there no way to do this and in that case why? I have been thinking of creating a new ResultType, but this seems like standard functionality. / Fredrik Lindberg (2012-09-26). On Wed, Sep 26, 2012 at 8:39 PM, Chris Pratt <[email protected]> wrote: > If you're configuring this in struts.xml, you're not in the browser (i.e. > presentation side), you're in the server! You either need to stream the > results directly from the server using one of the direct rendering engines > (jsp/freemarker/velocity/tiles) or you need to redirect to another URL or > Action. Maybe you need to take a step back and lay out exactly what you're > trying to accomplish. > (*Chris*) > > On Wed, Sep 26, 2012 at 10:15 AM, Fredrik Lindberg <[email protected]>wrote: > >> Hi! >> >> Yes, but then we are already on the presentation side of things. I >> want to forward to a different action and have it execute without a >> browser redirect. >> >> / Fredrik Lindberg (2012-09-26) >> >> On Wed, Sep 26, 2012 at 7:45 PM, Chris Pratt <[email protected]> >> wrote: >> > The default jsp/freemarker/velocity/tiles results do send the response >> > directly. The redirect & redirect-action results do exactly as you'd >> > expect and redirect the browser to retrieve the response. >> > (*Chris*) >> > >> > On Wed, Sep 26, 2012 at 9:30 AM, Fredrik Lindberg <[email protected] >> >wrote: >> > >> >> Hi! >> >> >> >> I am looking for if there is any alternative to the redirect-action >> >> result type where it does not generate a browser redirect? The issue >> >> with the browser redirect is that it results in a longer response >> >> times for the users and also means the server is put under higher load >> >> when it has to handle two requests in rapid succession (noticeable >> >> under high load). Also why not send what the client wants right away? >> >> >> >> I have read about request chaining and using the ChainingInterceptor, >> >> but this is fundamentally wrong in the sense that all request >> >> parameters that the first action was fed also are passed on to the >> >> next action. What I want is having control over what properties are >> >> passed on to the next action in the same way as for the redirects, but >> >> without the overhead. Can anyone help? =) >> >> >> >> / Fredrik Lindberg (2012-09-26). >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [email protected] >> >> For additional commands, e-mail: [email protected] >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
