wonder if this is a sideffect of wicket-tester? -igor
On 1/14/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
But that can then only be happening if the detach is called between rendering calls of specific components (so in one request) Then page get's detached (makes the version final) and then it renders again one or more component that again makes a new version all in the same request.. thats really bad.. johan On 1/14/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > Apparently the version number is upped by one. I saw this myself when > I did my first go at the problem... > > Martijn > > On 1/14/07, Johan Compagner <[EMAIL PROTECTED]> wrote: > > > > > > Oh and BTW once this test is fixed, IncrementalTableNavigationTest > > > will need to be updated. They are tied together as the number of > > > detachs has an impact on the generated behavior URLs apparently. > > > > > > > > really? > > detach is called after everything is generated. So how is the output > > different > > thats strange. > > > > johan > > > > > > > -- > Vote for Wicket at the > http://www.thebeststuffintheworld.com/vote_for/wicket > Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now! > http://wicketframework.org >
