struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ken McWilliams <ken.mcwilli...@gmail.com>
Subject Re: Redirect-action alternative in Struts2 without browser redirect
Date Wed, 26 Sep 2012 17:54:26 GMT
You _could_ (but in general certainly not _should_) create a new view
which only contains an action tag and use that for your result.

You can specify the desired parameters using the param tags, and you
can set executeResult to true so it then renders it's view.

On Wed, Sep 26, 2012 at 11:39 AM, Chris Pratt <thechrispratt@gmail.com> 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 <fredricus@gmail.com>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 <thechrispratt@gmail.com>
>> 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 <fredricus@gmail.com
>> >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: dev-unsubscribe@struts.apache.org
>> >> For additional commands, e-mail: dev-help@struts.apache.org
>> >>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Mime
View raw message