[TOMAHAWK-509] t:saveState does not check to see if the value attribute implements StateHolder.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.1.4-SNAPSHOT
• Assignee: Martin Marinschek
• Reporter: Matt Hughes
• Created: 30/Jun/06 02:14
• Updated: 14/Oct/06 22:23
• Resolved: 19/Sep/06 05:30

Description

The JavaDocs for t:saveState say (http://myfaces.apache.org/tomahawk/apidocs/org/apache/myfaces/custom/savestate/UISaveState.html ):

—
The object being saved must either:

• implement java.io.Serializable, or
• implement javax.faces.component.StateHolder and have a default constructor.

  ---

However, the component does nothing if the object implements StateHolder. If the object being saved does implement StateHolder and does not implement Serializable, the component should use the StateHolder mechanism of saveState()/restoreState(). This allows the object to determine what properties it actually wants to have saved.

Issue Links

• is blocked by: TOMAHAWK-738 SaveState fails with a java.util.List implementation other than ArrayList