Thabks for d'acces :)
Anyway, I'm happy to know tyou solved your problem, even if i dnd't help a
lot in the end .)
good luck with your tapestry project
2010/8/12 Josh Canfield
> > Thank you very much!!! This is great.
> > Now it works!
> Great!
>
> > I'm sorry for badly written question
>
> N
> Thank you very much!!! This is great.
> Now it works!
Great!
> I'm sorry for badly written question
No worries, I'm just lazy and don't want to have to think too hard ;)
-- Josh
On Aug 12, 2010, at 3:51 AM, Tornn wrote:
> Hi Josh!
>
> Thank you very much!!! This is great.
> Now it works
Hi Josh!
Thank you very much!!! This is great.
Now it works!
I'm not sure if this is last issue on my way, but this current issue
is solved. Thank you again.
p.s. I'm sorry for badly written question. I will try harder to
write good questions, which will save community time.
2010/8/12 J
Hi Katia
Thank you for you attention.
See answers below
12 августа 2010 г. 0:02 пользователь Katia Aresti Gonzalez
написал:
> I've checkout your code this afternoon in order to make it run. i didn't
> have much time, i had thing to do.
I uploaded war file for you:
http://tasks-journal.googlecode
Hi Karpushin Sergey.
>
Don't use ${} notation within bound parameters. This can cause
problems in other situations (casts the value to a string).
> The first problem is that tapestry cant automatically restore state
> of ActivityJournalItem component. When I receive event onSuccess for
> the
I've checkout your code this afternoon in order to make it run. i didn't
have much time, i had thing to do.
can you tell me all about your development and runtime environment, please ?
you are not using maven, are you using jetty to run the project ? tomcat ?
do I need to configure something in pa
So.., no one can help to solve this problem?
2010/8/11 Tornn :
> Hi Markus!
>
> Thank you for your response!
> I tried to do that. But if I add id="something${counter}" where
> counter is just a number it stops working at all.
> It renders ok. But buttons do nothing - they cannot submit the
Hi Markus!
Thank you for your response!
I tried to do that. But if I add id="something${counter}" where
counter is just a number it stops working at all.
It renders ok. But buttons do nothing - they cannot submit the form.
If I generate ${counter} as it Tapestry does ({"", "_0", "_1", ...
i meant to say
...
You are redering one component instance "activityJournalItem" in your loop,
three times the same component instance. inside this component a component
zone with t:id activityAjaxZone. in the end you are rendering the same
component all the time... as t:id are uniques
2010
Another person had the same problem (differently and more simple)
I copy the mail with a tapestry commiter answer :)
Hi!
if if call mutliple type my component like :
>
>
>
>
You have two different instances (objects) of your count component.
>
>
>
Now you have one instance being r
Hi,
The second problem and I can't find out how to solve it - tapestry
rerenders always first component instance ActivityJournalItem. If with
loop we rendered 3 times, not depending what button was pressed always
exactly first zone is rerendered.
I didn't check your code google project, but I had
Each zone in a loop must have a unique id, so you have to create an id
for example like this:
${zoneId}
private int idcounter;
public String getZoneId() {
return "randomtext" + idcounter++;
}
Otherwise only the first zone will be updated. Use id instead of t:id
for zones.
Hi All! You are
Hi All! You are my last hope. I tried to resolve it by myself, I asked
(http://tinyurl.com/2btkmzk) at stackoverflow.com but with no success
yet.
A little background. I'm very interested in tapestry (and currently
considering using it in production) because it looks like very
efficient (in all s
13 matches
Mail list logo
