On 9/20/10 12:30 PM, martinib wrote:
${customActionRedirect}?${urlParams}
true
I'm guessing there's some xml in there that some intermediate mail
process stripped out?
I set t
Hi, i'm using Struts 2.1.8.
I have this struts configuration
${customActionRedirect}?${urlParams}
true
I set the parameters to:
customActionRedirect="registrationConfirm"
urlParams
Dave Newton wrote:
You mean on a Result type?
On the "redirectAction" result type.
Personally I'd prefer this as the *default* behavior
and force you to specify if you *did* want "empty"
parameters included, but that's just me.
I agree, but I don't think the patch should change current beha
--- Dale Newfield <[EMAIL PROTECTED]> wrote:
> ...any struts committers reading this: If I
provided
> a patch for an extra specially named parameter like
> "supressEmptyParameters" that did just what you'd
> expect, what are the chances that someone would
> commit it?
You mean on a Result type?
Dave Newton wrote:
mySuccess
${fooId}
${barId}
Arguably, yes, and for a couple of reasons. Off the
top of my head I don't recall what will happen if the
param isn't found, though (or is null, etc.)
From reading the code it adds "¶m=" even if the param has no value,
which differs f
Dale Newfield wrote:
So it is clearly indicated that "redirectAction" is recommended over
"redirect", but I neither understand why, nor quite what it is that this
result type does...
If so, the new request needs to have the same URL (which must be encoded)
no matter which result type generated
--- Dale Newfield <[EMAIL PROTECTED]> wrote:
> So it is clearly indicated that "redirectAction" is
> recommended over "redirect", but I neither
> understand why, nor quite what it is that this
> result type does...
Precisely for the reasons stated; it adds a layer of
abstraction that understan
Gunnar Hillert wrote:
Thanks for your helpful post! Interestingly, this also works with redirect
actions.
Hrm...
The javadoc for ServletActionRedirectResult says:
This result uses the ActionMapper provided by the ActionMapperFactory
to redirect the browser to a URL that invokes the specified
Gunnar Hillert wrote:
Thanks for your helpful post!
You bet.
Interestingly, this also works with redirect
actions. Since I have not seen any examples anywhere out there, I thought I
also post an example for them:
mySuccess?fooId=${fooId}${bartId ? "&barId=" + bar
Most (all?) of the built-in result types parse OGNL in
the "location" param, although you can turn off that
functionality via the "parse" param.
d.
--- Gunnar Hillert <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Thanks for your helpful post! Interestingly, this
> also works with redirect
> actions.
Hi,
Thanks for your helpful post! Interestingly, this also works with redirect
actions. Since I have not seen any examples anywhere out there, I thought I
also post an example for them:
mySuccess?fooId=${fooId}${bartId ? "&barId=" + barId :
""}
Cheers,
11 matches
Mail list logo
