Well, I think treating them all as errors would likely break some
existing code. For example, the syntax is valid and useful in
read-only contexts, such as when the component parameter's default
binding prefix is BindingConstants.LITERAL and you want to pass a
dynamically-constructed string:
<html t:type="layout" title="${pageName}"
xmlns:t="http://tapestry.apache.org/schema/tapestry_5_1_0.xsd";>
I guess it's only when the default binding prefix is prop or var that
we can assume there is a real problem to warn about.
On Mon, Sep 19, 2011 at 1:21 PM, Thiago H. de Paula Figueiredo
<[email protected]> wrote:
> On Mon, 19 Sep 2011 13:40:51 -0300, Bob Harner <[email protected]> wrote:
>
>> I wonder if there's something that can be done to help, like making
>> the exception message more verbose about the common causes, or maybe
>> emitting a warning whenever ${...} is used in a component parameter in
>> a tml file and that parameter has a default binding prefix of "prop:"
>> or "var:"
>
> What about treating the use of expansions in parameters as an error
> outright? I can't think of any good reason for using expansions when passing
> parameters (and many for not).
>
> --
> Thiago H. de Paula Figueiredo
> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and
> instructor
> Owner, Ars Machina Tecnologia da Informação Ltda.
> http://www.arsmachina.com.br
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
