[PORTLETBRIDGE-37] VIEWSTATE_PARAM parsing in StateManager doesn't always work

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0-beta, 2.0.0-alpha
• Fix Version/s: 1.0.0-beta, 2.0.0-alpha
• Component/s: Impl
• Assignee: Michael Freedman
• Reporter: Michael Freedman
• Created: 17/Jun/08 21:20
• Updated: 09/Dec/08 19:18
• Resolved: 09/Dec/08 19:18

Description

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.