The API is pretty locked for now - only a significant bug found would cause a change. A significant bug is fairly unlikely considering that so many people are running production apps against it already and the changes from 1.3 -> 1.4 were not many (functionally).
I don't know about a date for 1.4 at this time - Igor? Frank / etc??? I just added a paragraph to the migration page regarding this change ( http://cwiki.apache.org/confluence/display/WICKET/Migrate-1.4#Migrate-1.4-getModelnamechange ). Hope this helps! -- Jeremy Thomerson http://www.wickettraining.com On Sun, Nov 23, 2008 at 6:31 PM, Susan Liebeskind < [EMAIL PROTECTED]> wrote: > Jeremy Thomerson wrote: > >> 1.4-rc1 is safe to go with (my opinion - i have quite a few apps currently >> deployed on various versions of 1.4 (m2 / m3 / and now rc1). >> >> > So long as the interfaces are NOT likely to make major changes (where major > = along the lines of the getModel -> getDefaultModel changeover), then I'm > okay with going with 1.4-rc1. I also noticed that the QuickStart maven > archetype works with 1.4-rc1 (it had problems with 1.4-m3 generics), so > that's also a good sign that 1.4rc1 is stable. > > And let me ask: is there any more resolution on when 1.4 final will be out, > given that RC1 is on the street? Or you just cannot predict a date at this > time? > > You go on to describe problems with differences between 1.3 / 1.4 - what >> errors are you specifically seeing? I think everything is pretty well >> documented, but something could be missed. The biggest difference (other >> than generics) was probably the getModel() -> getDefaultModel() change. >> >> > The POM file needed some fixing up due to changes in the Spring library > packaging - that was mentioned on the Wicket Migration page, so it was easy > to resolve that. It was the getModel->getDefaultModel change that took > some digging to find out, and which wasn't on the migration page. > If the powers that be could add something about the method name change to > the current migration page, that would be very helpful to others who will be > migrating from 1.3. I'm feeling a bit too new to the game to feek > comfortable updating the page (and that would also be making the assumption > that folks other than committers can add to the Wiki which I haven't yet > tried to do). > > Start a new thread for the errors you are seeing and we will help. >> >> > > Thanks. I know I can get rid of the compiler errors on my own (20+ uses of > the older get/setModel to replace), so I'm not too worried about that. > > But do you have a sense of any best practices/metaphors new for 1.4? I > don't see anything new on the wiki for 1.4 on the best practices page and > that's a more subtle issue when it comes to working with the newer release - > how should I be coding differently, if at all, now that we have this > genericized framework? Should I start a new thread about best practices for > 1.4? > > Thanks again. > > > Susan > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
