> the path in repeaters is never stable, it depends on a lot of factors > and is hard to predict. i think what may be a good way to deal with it > is to use an IComponentInstantiationListener to add a behavior to Item > subclasses to output their index in some attribute. install this > listener only during test time or simply make it output nothing if not > during the test. >
Interesting.... I'll look into it.. Is there really any reason why not to just always have the listener there. Seems like there would be little overhead in doing this... But I am curious, if this can be done then why couldn't the wicket page also be made stable using the same technique? >>>> 2) I have issues with timing which is typical, and most people call >>>> "waitForPageToLoad" which works fine for normal http requests, but if It >>>> is an ajax request I'm waiting for, then I have to implement a >>>> waitForContition. Is there a wicket convention I could use here? i.e. how >>>> can I know that a wicket ajax call has completed? >>> >>> there are global ajax callbacks that are invoked when an ajax request >>> completes. you can search this list for what they are. i imagine you >>> can write a bit of javascript to hook into those and implement >>> waitForCondition. >> >> I'm actually using the window.wicketGlobalPreCallHandler and >> window.wicketGlobalPostCallHandler in my code already. >> Do you think it would be safe to use those? I.E. preHander sets a boolean >> "isWaitingOnAjax" and postHander unsets it? >> >> Then I can do a waitForConition(!isWaitingOnAjax) > > yeah, that sounds like a good starting point. > > -igor > >> >>> >>> when you get all this working maybe you can create a wiki page about >>> it to help users who will have the same questions in the future. >> >> Sounds good... >> >>> >>> -igor >>> >>> >>>> >>>> Thanks, >>>> >>>> D/ >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
