I believe I tracked down the issue and have checked in a fix. https://issues.apache.org/jira/browse/TAP5-1613
This will go into the 5.3 release. I may have overlooked something obvious to someone else but I can't see a workaround for a 5.2.6 build. Josh On Sun, Aug 21, 2011 at 4:07 PM, Josh Canfield <joshcanfi...@gmail.com> wrote: > Ok, I've replicated the issue. > > Here is my update: > > Your ComponentClassTransformWorker is putting the mixin onto the > AbstractField instead of the Select component. AbstractField is what > implements getClientId, so this makes sense. What doesn't make sense > is that when the model for the Select component is generated the mixin > is added from the base class, but the order is not. > > Kids are waking up so I have to run! I'll dig more later, but it seems > like a defect? > > Josh > > On Sun, Aug 21, 2011 at 1:05 PM, Barry Books <trs...@gmail.com> wrote: >> FYI: If you want to see what my code does it's all here >> >> https://github.com/got5/tapestry5-jquery/blob/master/src/main/java/org/got5/tapestry5/jquery/services/RenderTrackerMixinWorker.java >> >> https://github.com/got5/tapestry5-jquery/blob/master/src/main/java/org/got5/tapestry5/jquery/mixins/Selector.java >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
