;session", "bean" and "firstname".
>
> Is this a bug or a feature?
> There are any restrictions for param names (no using of dots)?
>
> regards,
> Thomas
>
>
>
> --
> View this message in context:
> http://stru
nd "firstname".
Is this a bug or a feature?
There are any restrictions for param names (no using of dots)?
regards,
Thomas
--
View this message in context:
http://struts.1045723.n5.nabble.com/Param-names-with-spaces-tp5715585p5715589.html
S
>
> Is this a bug or a feature?
>
> regards,
> Thomas
>
>
>
> --
> View this message in context:
> http://struts.1045723.n5.nabble.com/Param-names-with-spaces-tp5715585p5715599.html
> Sent from the Struts - Dev mailing list archive at Nabble.com.
>
> -
and this doesnt work.
It seams so, that the ParametersInterceptor split these paramNames in
"session", "bean" and "firstname".
Is this a bug or a feature?
regards,
Thomas
--
View this message in context:
http://struts.1045723.n5.nabble.com/Param-names-with-spaces
2014-03-27 19:53 GMT+01:00 Paul Benedict :
> Spaces cannot exist for names of JavaBean properties. It doesn't make sense
> to have those.
But you can have map keys with spaces, i.e:
index.action?param['ble']=1¶m['ble ble']=2
Anyway, patch was improved and it isn't issue any more :-)
Regards
--
Spaces cannot exist for names of JavaBean properties. It doesn't make sense
to have those.
On Thu, Mar 27, 2014 at 1:54 AM, Lukasz Lenart wrote:
> Hi,
>
> I have applied patch attached to WW-4250 [1] to support Chinese
> characters as param names, but I figured out that I forgot to test
> that p
Hi,
I have applied patch attached to WW-4250 [1] to support Chinese
characters as param names, but I figured out that I forgot to test
that patch. After launching ParametersInterceptorTest just one test
failed - testParametersWithSpacesInTheName:
public void testParametersWithSpacesInTheName(
