« Return to Thread: Portlet namespace and request parameters
Re: Portlet namespace and request parameters
by Eric Dalquist
::
Rate this Message:
This is why forms must use POST and not GET. I'm not sure how the Pluto
driver handles this but uPortal, which uses the Pluto container,
differentiates between URL and form parameters and form parameters are
automatically associated with the portlet that generated the form's
action URL.
-Eric
Nils-Helge Garli Hegvik wrote:
> Hi!
>
> I was wondering if pluto should transparently support namespace
> encoding of request parameters? I tried adding the portlet namespace
> to some form elements, but they returned null when I tried getting
> them with portletRequest.getParameter(nonEncodedName). I'm aware that
> I don't have to encode form elements, but I believe I have seen other
> containers support this. If it does support it, and this is just a bug
> in my code, could you please tell me where the "decoding" of the
> request parameters happen?
>
> Nils-H
>
driver handles this but uPortal, which uses the Pluto container,
differentiates between URL and form parameters and form parameters are
automatically associated with the portlet that generated the form's
action URL.
-Eric
Nils-Helge Garli Hegvik wrote:
> Hi!
>
> I was wondering if pluto should transparently support namespace
> encoding of request parameters? I tried adding the portlet namespace
> to some form elements, but they returned null when I tried getting
> them with portletRequest.getParameter(nonEncodedName). I'm aware that
> I don't have to encode form elements, but I believe I have seen other
> containers support this. If it does support it, and this is just a bug
> in my code, could you please tell me where the "decoding" of the
> request parameters happen?
>
> Nils-H
>
smime.p7s (4K) « Return to Thread: Portlet namespace and request parameters
| Free embeddable forum powered by Nabble | Forum Help |
