On Sun, 21 Apr 2013 19:23:27 -0300, Bob Harner wrote:
Yes, this is such a common mistake that the error probably should be much
clearer.
I'd even suggest some configuration symbol (default value true) which
treats expansions in parameter values as template errors. (By the way, I'm
back. :
Yes, this is such a common mistake that the error probably should be much
clearer.
On Sun, Apr 21, 2013 at 11:27 AM, Todd Orr wrote:
> Thanks!
>
>
> On Sun, Apr 21, 2013 at 9:34 AM, Taha Siddiqi >wrote:
>
> > You can't use property expressions with component parameters
> >
> > You should try
>
Thanks!
On Sun, Apr 21, 2013 at 9:34 AM, Taha Siddiqi wrote:
> You can't use property expressions with component parameters
>
> You should try
>
>
>
>
> regards
> Taha
>
> On Apr 21, 2013, at 6:56 PM, Todd Orr wrote:
>
> > Why does this throw an exception?
> >
> >
> >
> >
> >
> >
You can't use property expressions with component parameters
You should try
regards
Taha
On Apr 21, 2013, at 6:56 PM, Todd Orr wrote:
> Why does this throw an exception?
>
>
>
>
>
>
>
>
>
>${title}
>
>
>
>
>
>
Why does this throw an exception?
${title}
Removing the second block delegate attempt works, but obviously doesn't
display the content. This fails the test of least surprise.
