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
