Maybe find the contributions in the source tree, look for references in the code to that filename. Set a breakpoint on the code that normally contributes it, run the old code that works.
When you hit the breakpoint, set more breakpoints a reasonably relevant distance back up the call chain (the caller, the caller's caller, etc). Now run it with the broken code and the breakpoints in the same places and see what decisions are being made differently, why the call chain never makes it as deep as the working configuration. You can do all this statically (i.e. with "find usages" searches), but the use of interfaces with multiple implementations can obscure the food chain unless you really know what to look for. On Nov 30, 2010, at 5:49 PM, Brad Grier wrote: > When I look at a diff from the ajax debug window between the failed 1.4.14 > request and the 1.4.12, it's obvious the wiquery javascript resources aren't > being contributed in the error scenarios. Any thoughts on where to look in > Wicket to see why these contributions are failing? > > -----Original Message----- From: Brian Topping > Sent: Tuesday, November 30, 2010 11:54 AM > To: users@wicket.apache.org > Subject: Re: Wicket 1.4.14 and WiQuery Tabs > > > On Nov 30, 2010, at 12:30 PM, Brad Grier wrote: > >> not sure how else to pin this down. > > If it were me, I would diff the generated HTML, then narrow down which > component(s) is/are causing the headache, THEN diff changes in those > components. As well because it's a great way to learn more about the code in > the process instead of just being numbed by the volume of changes... > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
