thank you for the great tip :)
> This is possible, isn't it?
>
> @InjectComponent
> private Zone myZone;
> public String getCurrentZoneId() {
> return "somethingUnique";
> }
> myZone will be treated like a normal component id by tapestry, and makes it
> possible to inject the zone in the clas
n commentRating.getBody();
>> >>> }
>> >>
>> >>> When I click on any t:actionlink updated rating for a context comment
>> >>> written in first rating "zone-div" element( which was rendered during
>> the
>>
This is possible, isn't it?
@InjectComponent
private Zone myZone;
public String getCurrentZoneId() {
return "somethingUnique";
}
myZone will be treated like a normal component id by tapestry, and makes it
possible to inject the zone in the class.
On Thu, May 14, 2009 at 9:08 AM, Yury Luneff
well, as for template -- it should work (not so much time need for
checking). as for zones injection in the page... well, i guess you
need to find a way of not injecting zones, there are different
possibilities that might work for you.
> How can I generate dynamic ID for zone?
> Can I use somethin
actionlink updated rating for a context comment
>> written in first rating "zone-div" element( which was rendered during the
>> first iteration )
>
>> What to do in such situations?
>
>
>
> -----------
i guess you should make different id's for all the zones you create
dynamically.
> Hello,
> This is my simple example code,
> tml:
>
> ${comment.rating}
> t:zone="commentRating">+
> t:zone="commentRating">-
>
> java:
> @InjectComponent
> private Zone commentRating;
> public Object onA
Hello,
This is my simple example code,
tml:
${comment.rating}
+
-
java:
@InjectComponent
private Zone commentRating;
public Object onActionFromVoteUp(Long commentId) {
voteService.voteUp(user, commentId);
comment = commentDao.findById(commentId);
return commentRating.getBody();
