In the project I'm working on, I don't have control over Bean design,
so this would be nice to have.
Also, for beans like this one:
class Order {
public String getOrderDescription();
public String getDescription();
}
Tapestry could simply work as it does today and not apply property
prefix stripping.
Adam
On Wed, May 25, 2011 at 12:20 PM, Lenny Primak <lpri...@hope.nyc.ny.us> wrote:
> At first glance, seems like a fantastic idea!
>
> On May 25, 2011, at 1:19 PM, Adam Zimowski wrote:
>
>> Since Tapestry already does tricks to clean up URL naming redundancy,
>> it would be nice if it did the same with the expression language. For
>> example:
>>
>> // Bean
>> class Order {
>> public String getOrderDescription() {...}
>> }
>>
>> // Page
>> public Order getOrder() {
>> //...
>> }
>>
>> // TML
>> Instead of having to say this: ${order.orderDescription}
>>
>> Perhaps this: ${order.description}
>>
>> Yes? No?
>>
>> Adam
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
