. As I said, I
was not consulted (and probably never will be).
From: Paul Bors p...@bors.ws
To: users@wicket.apache.org users@wicket.apache.org
Date: 01/03/2014 12:16 PM
Subject:Re: Rationale for Converting to AngularJS/Spring MVC
Both reasons provided don't
was not consulted (and probably never will be).
From: Paul Bors p...@bors.ws
To: users@wicket.apache.org users@wicket.apache.org
Date: 01/03/2014 12:16 PM
Subject:Re: Rationale for Converting to AngularJS/Spring MVC
Both reasons provided don't carry much wight
/03/2014 12:16 PM
Subject:Re: Rationale for Converting to AngularJS/Spring MVC
Both reasons provided don't carry much wight.
1) Dificulty of maintanance/upgrading between major releases
Our webapp was our reporting tool which morphed into a system
administative tool currently with 54k
: Rationale for Converting to AngularJS/Spring MVC
Both reasons provided don't carry much wight.
1) Dificulty of maintanance/upgrading between major releases
Our webapp was our reporting tool which morphed into a system
administative tool currently with 54k lines of code in well over 1k public
Hi,
On Fri, Jan 3, 2014 at 10:11 PM, Richard W. Adams rwada...@up.com wrote:
As to How was it difficult? Don't know. Nothing official came out. I'm
so low on the food chain I don't have many details. All I know is what
leaks out through the grapevine.
Good luck then: in the worse case you
I don't have first hand knowledge of the decision making process, but I
understand there were two main factors:
1. Difficulty in changing/maintaining the intermediate corporate
libraries, especially when considering whether to make the leap from
Wicket 1.4.17 to 6.x.
2. A perception of
Both reasons provided don't carry much wight.
1) Dificulty of maintanance/upgrading between major releases
Our webapp was our reporting tool which morphed into a system
administative tool currently with 54k lines of code in well over 1k public
classes (conform Sonar). I migrated the webapp
Hi,
On Fri, Jan 3, 2014 at 6:12 PM, Richard W. Adams rwada...@up.com wrote:
I don't have first hand knowledge of the decision making process, but I
understand there were two main factors:
1. Difficulty in changing/maintaining the intermediate corporate
libraries, especially when
takes. The high level
architects budgeteers have already decided our course, apparently.
From: Ernesto Reinaldo Barreiro reier...@gmail.com
To: users@wicket.apache.org
Date: 01/03/2014 12:59 PM
Subject:Re: Rationale for Converting to AngularJS/Spring MVC
Hi,
On Fri, Jan 3, 2014
