Hi,
On Fri, Jan 3, 2014 at 1:54 PM, Richard W. Adams <[email protected]> wrote: > My corporation has decided to change its standard Web framework from > Wicket to AngularJS/Spring MVCC (not my decision; was not asked for > input). I am faced with the expensive prospect of having to convert a > large app (runs on Jboss with about 250 Wicket/Web related classes). > > 1. Does anyone have experience in this kind of conversion, or know of Web > resources that could provide insight into best practices? > I do not know about best practices... I just did some experiments on using wicket + Angular JS in here 1-http://www.antiliasoft.com/wicket-angular-demo/ 2-https://github.com/reiern70/antilia-bits/tree/master/wicket-angular-parent > 2. My management is asking is if the conversion can be done incrementally > (because we still have to support the existing app until it's retired). I > interpret that to mean "Can an app have both Wicket & AngularJS/Spring MVC > pages at the same time?" From what I've read so far, Spring MVC & Wicket > can't coexist in the same app. (Though I'm hoping I'm wrong!) > > AFAIK Angular applications are single page WEB applications... Where all is fetched on one go and from there on Angular will take over to simulate navigation and so on... Sever side is just providing this initial load + RESTFUL WEB services to manage data. I do not see any reason why this cannot be done incrementally: i.e. porting some parts of the application. I also do not see a reason for Spring MVC and Wicket not been able to coexist. May I ask what was the rationale of choosing Angular JS + Spring MVC over Wicket? I have been using Backbone + Spring MVC in a project, imposed by client, for the last month and to be honest I'm not impressed with productivity you achieve using the combination: not to mention that developers need to know both JavaScript + Java server side to be completely productive. IMHO this will impact your productivity in a negative way. The only "reason" I could see to make that move is if scalability is an issue. Best regards, Ernesto
