Yes, I've finally resorted to data attributes. I wanted Tapestry-generated client ids for consistency, but it works either way.
On Wed, May 20, 2015 at 7:38 PM, Lance Java <lance.j...@googlemail.com> wrote: > Can you generate the clientId yourself and pass as a parameter into both > components? > > Why do you need to know the clientId? If it's for a javascript selector can > you use a data- attribute instead? > -- Ilya Obshadko
