Re: how to access client id of the component rendered later than the current one

Which component are we talking about here? Are you sure you're setting id (not to be confused with t:id, the serverside component id).

Re: how to access client id of the component rendered later than the current one

Inside a zone this id gets overridden by an automatically generated one. On Thu, May 21, 2015 at 7:45 PM, Lance Java wrote: > If you're solving it by explicitly setting a data attribute, why can't you > just explicitly set the id? > -- Ilya Obshadko

Re: how to access client id of the component rendered later than the current one

If you're solving it by explicitly setting a data attribute, why can't you just explicitly set the id?

Re: how to access client id of the component rendered later than the current one

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 wrote: > Can you generate the clientId yourself and pass as a parameter into both > components? > > Why do you need to know

Re: how to access client id of the component rendered later than the current one

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?

Re: how to access client id of the component rendered later than the current one

Thanks, that's helpful. I think that 'two components not in the same heartbeat' is really the reason, however I don't quite understand how to make them work in the same heartbeat and if that's even possible. Both components are rendered inside a zone, and the second one is a Bootstrap Affix, whic

Re: how to access client id of the component rendered later than the current one

Possibly a much simpler option is to explicitly provide a clientId

Re: how to access client id of the component rendered later than the current one

Can you include your template? Perhaps the two components are not within the same heartbeat. Depending on your use case, you might need a container component to invoke a method on a child at some later stage. Take a look at parallel / parallelContainer for inspiration http://t5stitch-lazan.rhclou

Re: how to access client id of the component rendered later than the current one

Interesting - I'm still receiving the same exception: java.lang.IllegalStateException: Unable to provide client id for component MyPage:component.name as it has not yet rendered. at org.apache.tapestry5.corelib.components.Any.getClientId(Any.java:135) at com.xdance.components.ScoreField.advised$de

Re: how to access client id of the component rendered later than the current one

Ah, thanks! That's what I was looking for, just forgot the name of annotation. On Tue, May 19, 2015 at 10:39 AM, Lance Java wrote: > Take a look at the Label component which uses @HeartbeatDeferred > -- Ilya Obshadko

Re: how to access client id of the component rendered later than the current one

Take a look at the Label component which uses @HeartbeatDeferred

how to access client id of the component rendered later than the current one

Is there any convenient way to do that? -- Ilya Obshadko