Re: upgrading Wicket
If I was a consulting company I'd also suggest rewriting in React. But upgrading to latest/greatest Wicket is not too bad, even if it is Wicket 1.4 code. There are gotcha's, but since probably the whole Wicket community upgraded their projects way before you guys, the issues are pretty much well documented in the migration guides. For now I'd suggest upgrading up to Wicket 9 at maximum, and see what breaks. Wicket 10 has the javax - jakarta package rename IIRC, so that will probably mean upgrading your complete stack. I don't know how many pages and custom components you need to migrate. At €dayjob we've upgraded our 3-4 major applications of in total 5M lines of code consistently, and typically the upgrades from 1.4 to 1.5 to 6 were the toughest. From there on it was not that hard (a couple of days for a major upgrade). But at that time, Wicket was really in heavy development and we did upgrade to betas all the time so there was usually some considerable rework necessary at that time to even out the wrinkles. Martijn On Fri, Jan 26, 2024 at 2:58 PM Nelligan, Steven M wrote: > > Help, I am new to Wicket...and have taken over a project with wicket > version 1.4.18, which is way out of date. > According to a consulting firm, this would be a multi-year project to > update all of our projects to the latest version of Wicket; and they are > recommending we just rewrite the front end code to React. > > Does anyone have a program or script which would help with the updating of > wicket components to a new Version? > > Thanks, > Steven M Nelligan > SENIOR SOFTWARE DEVELOPER > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com
Re: upgrading Wicket
Hi Steven, I undertook the Wicket Upgrade for a couple of 1.4/1.5 projects to Wicket 7/8 with Bootstrap. I don't have a script for upgrading it, but can share my experiences and component changes by early next week. If your 1.4 projects had multiple complex custom components written, then it might be just easier to either create a new project with the latest Apache Wicket and Wicket based UI libraries (which can replace some of your custom components) to retain and reuse Wicket knowledge, or, use React (or other Javascript framework). Using React compared to Apache Wicket would be an architectural shift and would need evaluating the pros/cons like budget, timeline, ability/requirement to write test cases for UI behavior, Java v/s JavaScript coding, overall testing, learning curve etc. Creating a new project with the latest Apache Wicket and UI component libraries might be easier than using React just with the fact that you already have 1.4 code to copy/paste many if not most of the codebase. In both cases, you can try to keep the UI leaner and push business to a separate web services based project. Best, -Mihir On Fri, Jan 26, 2024 at 8:58 AM Nelligan, Steven M wrote: > > Help, I am new to Wicket...and have taken over a project with wicket > version 1.4.18, which is way out of date. > According to a consulting firm, this would be a multi-year project to > update all of our projects to the latest version of Wicket; and they are > recommending we just rewrite the front end code to React. > > Does anyone have a program or script which would help with the updating of > wicket components to a new Version? > > Thanks, > Steven M Nelligan > SENIOR SOFTWARE DEVELOPER > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: upgrading Wicket
Hi Steven, I've send you a PM. Sven On 26.01.24 14:57, Nelligan, Steven M wrote: Help, I am new to Wicket...and have taken over a project with wicket version 1.4.18, which is way out of date. According to a consulting firm, this would be a multi-year project to update all of our projects to the latest version of Wicket; and they are recommending we just rewrite the front end code to React. Does anyone have a program or script which would help with the updating of wicket components to a new Version? Thanks, Steven M Nelligan SENIOR SOFTWARE DEVELOPER - 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
upgrading Wicket
Help, I am new to Wicket...and have taken over a project with wicket version 1.4.18, which is way out of date. According to a consulting firm, this would be a multi-year project to update all of our projects to the latest version of Wicket; and they are recommending we just rewrite the front end code to React. Does anyone have a program or script which would help with the updating of wicket components to a new Version? Thanks, Steven M Nelligan SENIOR SOFTWARE DEVELOPER - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Upgrading Wicket 1.2 site
I did a migration from 1.3.7 to 6.18 quite recently (main project plus shared sub-module). I found the process quite simple really and it was an opportunity to revisit some very poorly constructed code. My main problem wasn't so much with the migration itself but with my colleagues' code. Clearly the majority have very little understanding of the overall 'Wicket philosophy', the most egregious failing being a complete lack of understanding of the power of Wicket models and the pull model. This could also be an opportunity for you to take a step back and re-evaluate a lot of decisions both technical and functional (which regrettably wasn't possible in my case). Maybe Wicket isn't suitable for you anymore or maybe the rest of your project could use an architectural rethink. Good luck whatever you choose! CN -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Upgrading-Wicket-1-2-site-tp4671909p4671924.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Upgrading Wicket 1.2 site
Thanks for your comments. I think I will give up on the old code. Now I will have to decide whether to use Wicket for the rewrite or to switch to something entirely different. It's a fairly basic web shop, the backend is - Martijn, you guessed it! - Hibernate, Spring, JSF ;) and should not be changed (now). Are there any components or add-ons for Wicket that would help me with basic shop functionality like shopping cart, voucher handling, customer registration etc? Thanks Dennis -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Upgrading-Wicket-1-2-site-tp4671909p4671916.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Upgrading Wicket 1.2 site
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 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 > 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: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Upgrading Wicket 1.2 site
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 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: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Become a Wicket expert, learn from the best: http://wicketinaction.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Upgrading Wicket 1.2 site
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: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
