[TAP5-1614] Component Javadocs need clarification on encoder parameter being "required"

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.2.5
• Fix Version/s: 5.3
• Component/s: tapestry-core
• Labels: documentation
• Assignee: Bob Harner
• Reporter: Bob Harner
• Created: 24/Aug/11 02:18
• Updated: 15/Jan/12 14:53
• Resolved: 24/Aug/11 02:22

Description

Need to update javadocs to clarify the use of the encoder parameter when it is and isn't marked required, and to make the ValueEncoder phrasing more consistent from component to component. This is per the Aug 2011 conversation on the dev mailing list on the topic (http://tapestry.1045711.n5.nabble.com/Palette-and-Checklist-don-t-use-contributed-value-encoder-td4717507.html)