[
https://issues.apache.org/jira/browse/TAP5-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653612#action_12653612
]
Howard M. Lewis Ship commented on TAP5-79:
------------------------------------------
Coming along great so far; have ANTLR integrated.
However, something I didn't realize until just now: under the new scheme,
binding to "true" or "false" will be a full PropBinding instance, i.e.,
non-cacheable.
I think what I might do is add an internal marker annotation, @Invariant, that
can indicate to PropBinding instances that the value is invariant, even though
it looks like a property expression.
> T5 support for OGNL or OGNL-like expressions
> --------------------------------------------
>
> Key: TAP5-79
> URL: https://issues.apache.org/jira/browse/TAP5-79
> Project: Tapestry 5
> Issue Type: Improvement
> Affects Versions: 5.0.15
> Reporter: Dan Adams
> Assignee: Howard M. Lewis Ship
>
> While I really the use of prop and it's typesafeness, I still find myself
> frequently in need of more complicated expressions enough that I would be
> willing to pay the speed penalty of reflection in order to not have to define
> a public getter for it. In some situations, you can't actually make an
> equivilent getter. For instance, in integrations tests I've had more than one
> situation where I wanted to call a setter with a specific value from the
> template. With OGNL this is easy but with prop it's impossible. I would very
> much like to see prop remain the default binding but have OGNL available when
> it's needed. I think not having it would be a severe limitation of T5.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
