Re: [wsrp] public comment: navigational values on action URLs?

[Michael Freedman <michael.freedman@oracle.com>]

I believe it is really intended.  Navigational State is one of the 
mechanisms we provide for portlets to offload portlet state.  As a 
representation of portlet state its logical it be represented in all 
portlet URLs (even if indirectly because its implied) and passed to all 
portlet requests.  Yes, an action response sets new nav state so its 
conceivable for a portlet to merely encode some/all of the nav state it 
intends to return as interaction parameters having this clean separation 
gives clients/portlets much more flexibility in recognizing/processing 
incoming parameters.  I understand that JSR 168/286 made decisions that 
blends all of these back into a single concept (parameters) but that was 
its choice based in part of to the existing programming model (servlets).
   -Mike-

Stefan Hepper wrote:
> Is it really intended that you can set navigational values on an 
> action URL or is this an oversight in the URL BNF?
>
> I think result of the action should set new navigational values, but 
> not the submit of an action URL. Encoding new nav values will reset 
> whatever nav value other portlets have set in the meantime after the 
> URL has been generated.
> Is there really a use case to support this?
>
> Stefan
>