On 21.05.2012, at 20:07, Martin Marinschek <mmarinschek_at_apache.org> wrote:
>
>> Paul had made a case for supporting EL binding directly to JSON strings:
>>
>>> But if I should keep only one, it would be JSON only because it's
>> easy to transform a Map in a
>>> JSON array, but when I have real JSON (like when I have the
>> configuration of a jQuery UI widget),
>>> it's a bit heavy to be forced to use a Java method to transform it in
>> a Map.
>>
>> I don't quite get this - ie. I don't understand how jQuery comes into
>> the picture when EL binding to a Java managed bean.
>
> I guess the following is true: a JSF component renders a tag which is
> dynamically used by a JQuery widget. Additional configuration data
> (which jQuery needs to configure this widget) can be passed in with
> the data params.
Exactly. Modern web sites make heavy use of the data feature, because there is simple JavaScript access for them.
Frank