();
}
return o;
}
}
}
On Tue, Oct 25, 2011 at 2:14 PM, Brian Long wrote:
> Hi all,
>
> was hoping someone could point me in the direction on a good tutorial
> on the new property expressions in tapestry 5.2.6? I was using OGNL
> previously an
On Tue, 25 Oct 2011 14:57:50 -0200, Brian Long
wrote:
Hi Thiago,
Hi!
thanks for the quick reply, I'd already seen the official tapestry
property expressions page but as there's no examples given there I was
hoping there was something else buried in one of the wiki pages?
I
Hi Thiago,
thanks for the quick reply, I'd already seen the official tapestry
property expressions page but as there's no examples given there I was
hoping there was something else buried in one of the wiki pages?
I'll take your advise and move this logic to the java class, I
In Tapestry 4, we shifted a lot of logic into OGNL because that was
the only logic that could be reloaded (with the template) at runtime,
during development. This was good in some ways, OGNL is still more
versatile than Tapestry 5's property expressions, but came at a huge
cost in ter
On Tue, 25 Oct 2011 12:14:47 -0200, Brian Long
wrote:
Hi all,
Hi!
was hoping someone could point me in the direction on a good tutorial
on the new property expressions in tapestry 5.2.6?
http://tapestry.apache.org/property-expressions.html
I was using OGNL
previously and would like
Hi all,
was hoping someone could point me in the direction on a good tutorial
on the new property expressions in tapestry 5.2.6? I was using OGNL
previously and would like to update these expression to work with
ANTLR instead.
The ognl expression i had was to decorate text field with different
Hi,
I would like to that you and Gunnar Eketrapp for help. It works for me now.
thanks
Jan
Thiago H. de Paula Figueiredo wrote:
Em Wed, 02 Dec 2009 08:32:31 -0200, Jan Jirout
escreveu:
Hi,
Hi!
I have problem with property expression. When I try to use:
//
Never use ${} when pas
Em Wed, 02 Dec 2009 08:32:31 -0200, Jan Jirout
escreveu:
Hi,
Hi!
I have problem with property expression. When I try to use:
//
Never use ${} when passing parameters, as it converts its value to a
String. In this case, you needed a List.
--
Thiago H. de Paula Figueiredo
Independ
ail/3/2". But
> result URL is following:
> /
> /
>
> /http://localhost:8080/orderdetail/$005b223$002c$00201$005d/
>
>
> Context contains encoded sign like '[', ']' and ','. If I understand
> specification of property expressions at
> http://tapestry.
x27;[', ']' and ','. If I understand
specification of property expressions at
http://tapestry.apache.org/tapestry5.1/guide/propexp.html says than I
use valid format of context. I would like to use composite page link
context because I would like to have nice URL.
Can you pl
ollection. Thus
> ... should work.
>
> On Mon, Oct 5, 2009 at 8:39 AM, Brian Long wrote:
>
>> Hi all,
>>
>> just a quick question, looking at the property expressions guide @
>> http://tapestry.apache.org/tapestry5/guide/propexp.html it looks like I
>> shou
The not operator (!) coerces the value to a boolean; nil is false, as
is any kind of empty collection. Thus
... should work.
On Mon, Oct 5, 2009 at 8:39 AM, Brian Long wrote:
> Hi all,
>
> just a quick question, looking at the property expressions guide @
> http://tapestr
Hi all,
just a quick question, looking at the property expressions guide @
http://tapestry.apache.org/tapestry5/guide/propexp.html it looks like I
should be able to evaluate whether a property has a null value (handy
for if conditions) without having to use ognl,
e.g. instead of
...@gmail.com]
> Sent: 27 April 2009 17:29
> To: Tapestry users
> Subject: Re: T5.1 Property Expressions
>
> Congratulations, you have The JIRA Issue Of The Beast:
>
> https://issues.apache.org/jira/browse/TAP5-666
>
>
> On Thu, Apr 23, 2009 at 10:37 AM, Andy Blo
, 2009 at 10:37 AM, Andy Blower
> wrote:
> >
> > I just tried out the new T5.1 property expressions for the first time and
> got
> > an error. I’m trying to replace this:
> >
> > ${linkTitle}
> >
> > public String getLinkTitle() {
> >r
Congratulations, you have The JIRA Issue Of The Beast:
https://issues.apache.org/jira/browse/TAP5-666
On Thu, Apr 23, 2009 at 10:37 AM, Andy Blower
wrote:
>
> I just tried out the new T5.1 property expressions for the first time and got
> an error. I’m trying to replace this:
>
&
Looks like a bug to me.
On Thu, Apr 23, 2009 at 10:37 AM, Andy Blower
wrote:
>
> I just tried out the new T5.1 property expressions for the first time and got
> an error. I’m trying to replace this:
>
> ${linkTitle}
>
> public String getLinkTitle() {
> return getTi
Have you tried ${getTitle('false')}?
Uli
Andy Blower schrieb:
I just tried out the new T5.1 property expressions for the first time and got
an error. I’m trying to replace this:
${linkTitle}
public String getLinkTitle() {
return getTitle(false);
}
With this:
${getT
I just tried out the new T5.1 property expressions for the first time and got
an error. I’m trying to replace this:
${linkTitle}
public String getLinkTitle() {
return getTitle(false);
}
With this:
${getTitle(false)}
Which I should be able to do according to the Grammar as far
19 matches
Mail list logo