Sounds like a potential ognl bug as well. The (index + 1) expression
should be interpreted as a separate addition expression from
everything else.
If you would be so kind as to file an issue here:
http://jira.opensymphony.com/browse/OGNL
I can take a look at fixing it during the next release.
Thx Richard,
In your opinion whats better/smarter:
1) "ognl:id + '-cg-' + (index * 1 + 1)"
2)"ognl:id + '-cg-' + add(index,1)"
?
On 1/24/07, Richard Clark <[EMAIL PROTECTED]> wrote:
On 1/24/07, Andrea Chiumenti <[EMAIL PROTECTED]> wrote:
> "ognl:id + '-cg-' + (index + 1)"
>
> the index is an
On 1/24/07, Andrea Chiumenti <[EMAIL PROTECTED]> wrote:
"ognl:id + '-cg-' + (index + 1)"
the index is an int property.
I expect the result to be:
comp-cg-1
etc. but instead I've back
comp-cg-01
It's ugly, but one answer is "ognl:id + '-cg-' + (index * 1 + 1)",
using the multiplication to fo
hello,
I have an ognl expression inside a @For component and I'm using tap 4.1.1
"ognl:id + '-cg-' + (index + 1)"
the index is an int property.
I expect the result to be:
comp-cg-1
comp-cg-2
comp-cg-3
etc. but instead I've back
comp-cg-01
comp-cg-11
comp-cg-21
How to sum index + 1 and append
ark
Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
-Original Message-
From: Robert Zeigler [mailto:[EMAIL PROTECTED]
Sent: Wed 11/22/2006 12:01 PM
To: Tapestry users
Subject: Re: Help with ognl...
the binding type for default-value is
the binding type for default-value is already ognl. So ognl is chocking
on the ognl: part. Try something like:
default-value="false"
:)
Robert
Mark Stang wrote:
> I am trying to create a 3.x parameter:
>
> direction="in" default-value="ognl:@[EMAIL PROTECTED]"/>
>
> I was using a "boolean
I am trying to create a 3.x parameter:
I was using a "boolean", but there is a bug in 3.x where sometimes it doesn't
pass the value in, so I switched to a Boolean, but can't seem to come up with a
valid default value.
Unable to parse expression 'ognl:@[EMAIL PROTECTED]'.
binding:
