You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Ate Douma (JIRA)" <je...@portals.apache.org> on 2009/04/16 11:32:14 UTC
[jira] Resolved: (JS2-968) Enhance NavigationalState encoding to
support both zero and empty parameter values
[ https://issues.apache.org/jira/browse/JS2-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ate Douma resolved JS2-968.
---------------------------
Resolution: Fixed
Done
> Enhance NavigationalState encoding to support both zero and empty parameter values
> ----------------------------------------------------------------------------------
>
> Key: JS2-968
> URL: https://issues.apache.org/jira/browse/JS2-968
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Components Core
> Affects Versions: 2.2.0
> Reporter: Ate Douma
> Assignee: Ate Douma
> Fix For: 2.2.0
>
>
> For the new JSR-286 Public Render Parameters it is required to encode the intended removal of parameter.
> The current NavigationalState encoding/decoding (JetspeedNavigationalStateCodec) however always expects at least one (non-empty) value to be provided.
> In addition, and something which has been an oversight so far, it is valid to set empty parameter value(s) for a parameter, both for the servlet api and the portlet api (1.0 and 2.0).
> I'll update the NavigationalState encoding/decoding to deal with both requirements: null and empty parameter values, whereas a null value is only allowed for encoding the removal of a public render parameter (doesn't apply to "private" parameters).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org