[
https://issues.apache.org/jira/browse/TAPESTRY-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship updated TAPESTRY-1624:
-------------------------------------------
Priority: Major (was: Critical)
Fix Version/s: 5.0 Next Release
I'd like to extend the property expression language quite a bit more, but keep
it concise and type safe. But not before first stable release.
> T5 support for OGNL or OGNL-like expressions
> --------------------------------------------
>
> Key: TAPESTRY-1624
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1624
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Dan Adams
> Fix For: 5.0 Next Release
>
>
> 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]
