I guess you will need to refresh the UI as well, i.e. make the app look nicer than what the web designer created N years ago. So you will have to update it completely. I'd suggest to start from scratch. But in case you decide to migrate it - don't hesitate to ask here!
Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Sep 7, 2015 at 3:16 PM, Martijn Dashorst <[email protected] > wrote: > Probably you're asking this question on the Hibernate lists as well: > does it make sense to upgrade from Hibernate 1.2 to 5? And on the > Spring list as well. :-) > > It depends: it is totally dependent on the quality of the code in the > first place. It is quite a lot years you'll need to update. One of the > biggest challenges will be the upgrade to Java 5. There's not too much > information available on the upgrade path from 1.2 to 1.5. 1.5 -> 6 is > described somewhat decent, and 6->7 is a quite easy upgrade. > > Martijn > > > > On Mon, Sep 7, 2015 at 2:03 PM, Dennis Luemkemann > <[email protected]> wrote: > > Hello all, > > > > I inherited a site built with Wicket 1.2. Now we need a lot of new > features, basically a site relaunch, and I’m wondering what would be the > best approach. I’m not too familiar with Wicket and the changes in the API > over the years. Does it make sense to upgrade the current site to an > up-to-date version of Wicket and then add new functions, or are the changes > in the framework so extensive that it would be better to start off from > scratch with a current version of Wicket and re-implement the still needed > existing stuff? > > > > Best regards > > Dennis > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
