Thanks Kev for stepping up.
 
Yes it appears to be an id dilemma and no logic is in place to accomodate 
multiple references to a single instance in this dom space since ALL id's to 
ALL dom nodes within the same dom child collection need to be unique.
 
So I'm stuck. Sorry about the fumes... but I been beating this horse dead for 
3.5 months believing that tapestry 4.1.3 worked. If I am mistaken, I'd like to 
hear about what logic is in place to resolve multiple references to BLOCK 
declarations as they are used in RenderBlock.
 
I still wonder why my originally specified ID's were not used. It's like the 
generated ones overwrote the hashkey to the component. That must be it.
 
Well I'd like to hear about some workaround considerations from the tapestry 
pro's. 
 
Any takers?
 
Thanks
Ken
_________________________________________________________________
Climb to the top of the charts! Play the word scramble challenge with star 
power.
http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_jan

Reply via email to