>>>>> On Sat, 19 May 2012 15:13:25 +0200, Martin Marinschek <martin.marinschek_at_gmail.com> said:
MM> I think that you are right: if we do this, then all over the
MM> place. I have once built a version of a data table which could build
MM> its model from a JSON like string.
MM> That was nice for RAD, where you don't want to create a Java class
MM> for starting out.
Rather than put "data" everywhere, let's just put it on
<f:dataAttribute>. So you'd have
<f:dataAttribute name="foo" value="bar">
or
<f:dataAttribute json="{ foo : bar}" />
Of course, EL expressions are valid en all places.
For completeness, we'd need to decide which takes precedence, and in
this case it's simpler to say that if the json attribute is present, all
other attributes are ignored.
Ed
--
| edward.burns_at_oracle.com | office: +1 407 458 0017
| homepage: | http://ridingthecrest.com/