Hi, after quite a while using Tapestry I've got a situation where I need an 
event handler that accepts an unknown amount multiple parameters.

mark(boolean checked, String[] itemIds)
mark(boolean checked, String... itemIds)
mark(boolean checked, List<String> itemIds)

I've tried these and the Last one works after a fashion. Basically the first 
element of the itemIds list is the checked Boolean value in string form. This 
seems like a bug to me, but I've been struggling to get this working so I might 
be being stupid here. What do you all think?

Also, Tapestry doesn't appear to be able to distinguish between that method 
signature and this

mark(boolean checked, String itemId)

which does tie up with the documentation I suppose, but this is  why I was 
trying the String... way. Anyway I can use two different events to get round 
this.

Thanks,

Andy.

Reply via email to