[TAP5-1244] Tapestry components and mixins should be converted to use JavaScriptSupport, not RenderSupport

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.2.1
• Fix Version/s: 5.2.1
• Component/s: tapestry-component-report
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 12/Aug/10 21:06
• Updated: 19/Aug/10 21:45
• Resolved: 19/Aug/10 20:53

Description

The Autocomplete mixin is an example; since it uses RenderSupport, it means lots of unwanted calls to Tapestry.init() on the client side.

However, this may be related to another bug about JavaScriptSupport not supported client-side initializer functions that take JSONArray (rather than a String or JSONObject).