I'd go even further: all literal or ognl makes no sense, especially
all ognl. Plain HTML tag attributes are literal, so why should the
component tag attributes in HTML be any different?
On a more pragmatic note, if we add or remove the jwcid="...", then
we have to modify attribute values. No thanks! In the context of
HTML templates, literal is the natural default.
Similarly if we look at .page files the most common binding is ognl.
Prefixing ognl everywhere would be redundant and distracting. Tapestry
version 3 had it right: ognl is the natural default for spec files.
Cheers,
Nick.
Jamie Orchard-Hays wrote:
I must say I don't understand the desire to have a it all literal or
all ognl between specs and templates. I have thought ognl in specs and
literal in templates made absolutely perfect sense in 3.
Jamie
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
