tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-1521) JavaScriptSupport.addInitializerCall() should support JSONArray of function parameters, as RenderSupport does
Date Wed, 11 May 2011 02:03:47 GMT

     [ https://issues.apache.org/jira/browse/TAP5-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship closed TAP5-1521.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.3.0

> JavaScriptSupport.addInitializerCall() should support JSONArray of function parameters,
as RenderSupport does
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1521
>                 URL: https://issues.apache.org/jira/browse/TAP5-1521
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.3.0, 5.2.5
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.3.0
>
>
> JavaScriptSupport does not support addInitializerCall(String,JSONArray), which is supported
by RenderSupport. This was intentional, as using a JSONObject (with named key/values) is less
likely to cause problems coordinating server-side Java code with client-side JavaScript code.
> However, it can be unwieldy and verbose as well.  Therefore, it should be re-implemented
efficiently ... RenderSupport.addInit(String,JSONArray) still works, but is implemented in
a very inefficient way.  Instead, it should pass through to new method JavaScriptSupport.addInitializerCall(String,JSONArray).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message