[jira] Commented: (PORTLETBRIDGE-37) VIEWSTATE_PARAM parsing in StateManager doesn't always work

["Michael Freedman (JIRA)" <de...@myfaces.apache.org>]

    [ https://issues.apache.org/jira/browse/PORTLETBRIDGE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616708#action_12616708 ] 

Michael Freedman commented on PORTLETBRIDGE-37:
-----------------------------------------------

This has been fixed in the Portlet 1.0 Bridge codeline but hasn't yet been fixed in the 2.0 codeline hence the bug is left open as a reminder to merge the work.

> VIEWSTATE_PARAM parsing in StateManager doesn't always work
> -----------------------------------------------------------
>
>                 Key: PORTLETBRIDGE-37
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-37
>             Project: MyFaces Portlet Bridge
>          Issue Type: Bug
>          Components: Impl
>    Affects Versions: 1.0.0, 2.0.0
>            Reporter: Michael Freedman
>            Assignee: Michael Freedman
>
> Currently the code that parses for the VIEWSTATE_PARAM in the Bridge's StateManager is rudimentary (primarily for performance reasons).  If checks to see if there is a closing /> to ensure it doesn't read beyond the end of the tag.  However some environment (Trinidad) close the element just with a '>'.  When this check fails we return null meaning the parameter isn't located/preserved.  State is lost by the bridge.  The bridge should be more tolerant.  At a minimum it should recognize either end of tag.  But failing this and other checks it should do more extensive parsing to ensure proper execution -- i.e. it should work regardless of whether the name field is before the value field and/or '>' is a character in the view state param's value.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.