Yes,
using ${request.getParameter('teste')} instead of ${request.teste} makes
the diference.
Thanks Reinhard for the help.
Rui
On Tue, 2005-06-07 at 09:17 +0200, Geert Josten wrote:
> >>> Have you tried cocoon.request.getParameter('test') instead of
> >>> cocoon.request.test?
> >>
> >> I don't think getParameter will make a difference.
> >
> > Citing http://wiki.apache.org/cocoon/RequestParameterEncoding
> >
> > [...]
> > For Java-insiders: what Cocoon actually does internally is apply the
> > following trick to get a parameter correctly decoded: suppose "value" is
> > a string containing a request parameter, then Cocoon will do:
> >
> > value = new String(value.getBytes("ISO-8859-1"), "UTF-8");
> > [...]
> >
> > IIRC, the property reflection methods don't use this ... but maybe I'm
> > wrong.
>
> I was thinking that getting a property was simply translated to a
> getParameter by the FOM wrapper,
> but I guess you are right. Properties are handled by the Rhino interpreter
> (JS Flowscript), while
> getParameter is a function in the FOM request wrapper object.
>
> :-P
>
> (sorry ;)
>
> G.
>
> ---------------------------------------------------------------------
> 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]
