I have to agree with the other guys You were starting to get on my tits a
bit too.
In fact, if you look at the first response on this thread, I provided a link
to an example [1] containing the solution to your problem. I get the feeling
that you don't take the time to comprehend (or maybe
but it also states that there is a bug with parameters
sarcasticI love it when people who don't understand something say it's
broken/sarcastic
public MapString, String getFoo() {
// return a map
}
t:eventlink parameters=foo.../t:eventlink
--
View this message in context:
java.lang.Integer to type java.util.Map.
From: kcola...@live.com
To: users@tapestry.apache.org
Subject: RE: EventLink parameters
Date: Tue, 16 Oct 2012 00:28:31 -0400
alright lance... your context works... but it also states that there is a bug
with parameters... you hadnt mentioned that
kcola
so context was the solution... i get my pagenumber in nicely to the handler
t:eventLink t:id=IndividualPage t:context=${pageValue}
thanks for helping
: )
From: kcola...@live.com
To: users@tapestry.apache.org
Subject: RE: EventLink parameters
Date: Tue, 16 Oct 2012 10:28:38 -0400
eventlink.parameters MUST be either a Map or something that can be coerced to
a Map
eventlink.context MUST be either a collection or something that can be
coerced to a collection (eg a single value)
--
View this message in context:
On Tue, 16 Oct 2012 11:30:49 -0300, Ken in Nashua kcola...@live.com
wrote:
t:eventLink t:id=IndividualPage t:context=${pageValue}
Never, never ever use ${} expansions when passing parameters values.
--
Thiago H. de Paula Figueiredo
you.
I will keep on developing tapestry because its my passion.
peace be with you
From: kcola...@live.com
To: users@tapestry.apache.org
Subject: RE: EventLink parameters
Date: Tue, 16 Oct 2012 10:30:49 -0400
so context was the solution... i get my pagenumber in nicely to the handler
will be in a position
to understand why your questions are not the right questions.
Best of luck
Taha
On Oct 17, 2012, at 9:02 AM, Ken in Nashua wrote:
Subject: Re: EventLink parameters
From: lpri...@hope.nyc.ny.us
Date: Tue, 16 Oct 2012 11:06:10 -0400
To: kcola...@live.com
Seriously, I hate
Thanks Taha... but I got a huge problem understanding this language and I am
not talking about T5.
I am having fun with this T5... real diamond grade fun.
Is that such a crime ?
I can model the natural world... am I not allowed?
I enjoy the ups and downs and challenges and problems.
I dont
t:parameters=prop:{'pageNum':'indexValue'}
t:parameters=prop:{'pageNum':'${pageIndex}'}
Lance, thats just the problem... I did just that and it doesnt work.
indexValue and pageIndex are both from within the java
Just write a getter (aka a property)
public int getFoo() {
// return some calculation using pageNum and index value
}
And call it in a template
t:eventlink context=foo.../t:eventlink
--
View this message in context:
use a java method or try to
dereference a java method
kcola...@live.com
From: kcola...@live.com
To: users@tapestry.apache.org
Subject: RE: EventLink parameters
Date: Mon, 15 Oct 2012 16:20:46 -0400
t:parameters=prop:{'pageNum':'indexValue'}
t:parameters=prop:{'pageNum':'${pageIndex
alright lance... your context works... but it also states that there is a bug
with parameters... you hadnt mentioned that
kcola...@live.com
From: kcola...@live.com
To: users@tapestry.apache.org
Subject: RE: EventLink parameters
Date: Mon, 15 Oct 2012 17:43:37 -0400
Lance, this has
It looks like you're trying to do too much logic in a template again. Write a
getter for your logic and access the simplified property in your template.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/EventLink-parameters-tp5716874p5716886.html
Sent from the Tapestry -
I suggest you get my gallery example up and running from this thread
tapestry.1045711.n5.nabble.com/Gallery-for-each-article-using-hibernate-td5716817.html
Note how I do the work in a getter so that every request will invoke it.
Note also that it does not use @Persist.
--
View this message in
event link parameters is very sensitive
t:parameters=prop:{'pageNum':'indexValue'}
this compiles and runs but doesnt give me what i want
t:parameters=prop:{'pageNum':'2'}
this compiles and runs but doesnt give me what i want
t:parameters=prop:{'pageNum':'${pageIndex} + 2'}
16 matches
Mail list logo
