What are you talking about? 1.2.6 is binary compatible with 1.2.2, or at least that should be the case. If it is not, then that is a bug.
Martijn On 6/26/07, Nili Adoram <[EMAIL PROTECTED]> wrote: > even upgrade to 1.2.6 is involved with lots of adoptions. > the question is whether it will solve this issue. > > Timo Rantalaiho wrote: > > On Tue, 26 Jun 2007, Nili Adoram wrote: > > > >> I am afraid I cannot upgrade at the moment since we don't have the time > >> for massive API changes of 1.3. > >> > > > > 1.2.2 is really ancient, you should use 1.2.6. > > > > - Timo > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > -- Wicket joins the Apache Software Foundation as Apache Wicket Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.6 contains a very important fix. Download Wicket now! http://wicketframework.org ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
