You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by "Richard W. Adams" <RW...@UP.COM> on 2014/01/03 13:54:52 UTC
Converting Wicket to AngularJS/Spring MVC
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?
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!)
**
This email and any attachments may contain information that is confidential and/or privileged for the sole use of the intended recipient. Any use, review, disclosure, copying, distribution or reliance by others, and any forwarding of this email or its contents, without the express permission of the sender is strictly prohibited by law. If you are not the intended recipient, please contact the sender immediately, delete the e-mail and destroy all copies.
**
Re: Rationale for Converting to AngularJS/Spring MVC
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
Hi,
On Fri, Jan 3, 2014 at 10:11 PM, Richard W. Adams <RW...@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 will learn new technologies and gain
experience on technologies that start to be "hot"
Re: Rationale for Converting to AngularJS/Spring MVC
Posted by "Richard W. Adams" <RW...@UP.COM>.
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.
In any case, whether the new frameworks will be better worse. I have no
influence over what course the corporation takes. The high level
architects & budgeteers have already decided our course, apparently.
From: Ernesto Reinaldo Barreiro <re...@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 at 6:12 PM, Richard W. Adams <RW...@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 considering whether to make the leap from
> Wicket 1.4.17 to 6.x.
>
How was it difficult?
>
> 2. A perception of excessive cost in training new developers to use
> Wicket. I myself am fairly comfortable with Wicket now (after 2 years
> experience), but have to admit the leaning curve was pretty steep.
>
IMHO this is not going to improve with Angular.SJ+ Spring MVC: its is
going to be worse.
1-With wicket you might hire a very good wicket developer that creates the
components / widgets you need and the rest of the team just use those
components and be "shielded" form JavaScript and mostly just do "server
side". With Angular you will need more developers covering the whole stack
(sever side and client side).
2-You can also reuse code at a maximum and if you have a lot of
applications/similar screen you can roll out "meta components" covering
those use cases... Not sure you will be able to achieve the same so easily
with Angular.JS + Spring MVC.
As I mentioned before I was working last three weeks with an application
built with Backbone.JS (similar to Angular but less high level) + Spring
MVC. All the "complexities" of this application would be mostly trivial
using wicket. One thing that stoke me the most if the non DRYNESS of
development: you change one thing at a place and you have to manually hunt
down in all layers how this trivial change will impact application.
**
This email and any attachments may contain information that is confidential and/or privileged for the sole use of the intended recipient. Any use, review, disclosure, copying, distribution or reliance by others, and any forwarding of this email or its contents, without the express permission of the sender is strictly prohibited by law. If you are not the intended recipient, please contact the sender immediately, delete the e-mail and destroy all copies.
**
Re: Rationale for Converting to AngularJS/Spring MVC
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
Hi,
On Fri, Jan 3, 2014 at 6:12 PM, Richard W. Adams <RW...@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 considering whether to make the leap from
> Wicket 1.4.17 to 6.x.
>
How was it difficult?
>
> 2. A perception of excessive cost in training new developers to use
> Wicket. I myself am fairly comfortable with Wicket now (after 2 years
> experience), but have to admit the leaning curve was pretty steep.
>
IMHO this is not going to improve with Angular.SJ+ Spring MVC: its is
going to be worse.
1-With wicket you might hire a very good wicket developer that creates the
components / widgets you need and the rest of the team just use those
components and be "shielded" form JavaScript and mostly just do "server
side". With Angular you will need more developers covering the whole stack
(sever side and client side).
2-You can also reuse code at a maximum and if you have a lot of
applications/similar screen you can roll out "meta components" covering
those use cases... Not sure you will be able to achieve the same so easily
with Angular.JS + Spring MVC.
As I mentioned before I was working last three weeks with an application
built with Backbone.JS (similar to Angular but less high level) + Spring
MVC. All the "complexities" of this application would be mostly trivial
using wicket. One thing that stoke me the most if the non DRYNESS of
development: you change one thing at a place and you have to manually hunt
down in all layers how this trivial change will impact application.
Re: Rationale for Converting to AngularJS/Spring MVC
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
Hi,
On Tue, Jan 7, 2014 at 4:48 PM, Dan Simko <wi...@gmail.com> wrote:
> Hi,
>
> I didn't read whole conversation but you don't need to choose between
> Wicket and AngularJS. We are using both technologies together and it works
> great. AngularJS has no global state so you can use many Angular ("island"
>
That's exactly what the demo mentioned does: it creates a page where all
logic/AJAX is done via Angular and Wicket page just acts as a script
generating the page.
> single page) apps in one Wicket page. For some use-cases is better Wicket
so you use Wicket and for some (not so many) is better Angular, so you
> embed Angular app to Wicket page.
>
> Best regards,
> Dan Simko
>
>
> On Tue, Jan 7, 2014 at 8:37 AM, Martin Grigorov <mgrigorov@apache.org
> >wrote:
>
> > Make some noise about this (stupid) decision and when the higher
> management
> > realize the mistake they made they will ask you ;-)
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> >
> >
> > On Mon, Jan 6, 2014 at 3:11 PM, Richard W. Adams <RW...@up.com>
> wrote:
> >
> > > Whether the reasons are valid or not irrelevant. I only passed along
> what
> > > I have heard; don't necessarily agree with the rationales. As I said, I
> > > was not consulted (and probably never will be).
> > >
> > >
> > >
> > >
> > > From: Paul Bors <pa...@bors.ws>
> > > To: "users@wicket.apache.org" <us...@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.
> > >
> > > 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 from Wicket 1.3.x to 6.x
> > by
> > > myself in under 2 weeks simply by following the migration tutorials one
> > by
> > > one.
> > >
> > > 2) Cost of tranning new developers
> > > Wicket itself is model much after the Java's Swing and it promotes
> > > fast
> > > adaptation for new developers (they teach Swing in college). Perhaps
> the
> > > new staff should consider spending 1 to 2 weeks reading one of the many
> > > books avaialble on Wicket, see:
> > > http://wicket.apache.org/learn/books/
> > >
> > > I spent a good 3-4 weeks reading over Andreas' free guide whcih took so
> > > long because I was reading it a chpater a day on the subway ride to
> work
> > > while at the same time proof reading his new material. You can print
> the
> > > free guide via:
> > > http://wicket.apache.org/start/userguide.html
> > >
> > > I don't know AngualrJS too much as I never worked with it. To me it
> looks
> > > like another JS framework out there in the mixture of many that can
> very
> > > easily be integrated with Wicket. Perhaps you should suggest that to
> your
> > > upper management.
> > >
> > > Anyhow, that's my two cents.
> > >
> > >
> > > On Fri, Jan 3, 2014 at 12:12 PM, Richard W. Adams <RW...@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 considering whether to make the leap from
> > > > Wicket 1.4.17 to 6.x.
> > > >
> > > > 2. A perception of excessive cost in training new developers to use
> > > > Wicket. I myself am fairly comfortable with Wicket now (after 2 years
> > > > experience), but have to admit the leaning curve was pretty steep.
> > > >
> > > >
> > > >
> > > >
> > > > From: Ernesto Reinaldo Barreiro <re...@gmail.com>
> > > > To: users@wicket.apache.org
> > > > Date: 01/03/2014 10:58 AM
> > > > Subject: Re: Converting Wicket to AngularJS/Spring MVC
> > > >
> > > >
> > > >
> > > > 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
> > > >
> > > >
> > > >
> > > > **
> > > >
> > > > This email and any attachments may contain information that is
> > > > confidential and/or privileged for the sole use of the intended
> > > recipient.
> > > > Any use, review, disclosure, copying, distribution or reliance by
> > > others,
> > > > and any forwarding of this email or its contents, without the express
> > > > permission of the sender is strictly prohibited by law. If you are
> not
> > > the
> > > > intended recipient, please contact the sender immediately, delete the
> > > > e-mail and destroy all copies.
> > > > **
> > > >
> > >
> > >
> > >
> > > **
> > >
> > > This email and any attachments may contain information that is
> > > confidential and/or privileged for the sole use of the intended
> > recipient.
> > > Any use, review, disclosure, copying, distribution or reliance by
> > others,
> > > and any forwarding of this email or its contents, without the express
> > > permission of the sender is strictly prohibited by law. If you are not
> > the
> > > intended recipient, please contact the sender immediately, delete the
> > > e-mail and destroy all copies.
> > > **
> > >
> >
>
--
Regards - Ernesto Reinaldo Barreiro
Re: Rationale for Converting to AngularJS/Spring MVC
Posted by Dan Simko <wi...@gmail.com>.
Hi,
I didn't read whole conversation but you don't need to choose between
Wicket and AngularJS. We are using both technologies together and it works
great. AngularJS has no global state so you can use many Angular ("island"
single page) apps in one Wicket page. For some use-cases is better Wicket
so you use Wicket and for some (not so many) is better Angular, so you
embed Angular app to Wicket page.
Best regards,
Dan Simko
On Tue, Jan 7, 2014 at 8:37 AM, Martin Grigorov <mg...@apache.org>wrote:
> Make some noise about this (stupid) decision and when the higher management
> realize the mistake they made they will ask you ;-)
>
> Martin Grigorov
> Wicket Training and Consulting
>
>
> On Mon, Jan 6, 2014 at 3:11 PM, Richard W. Adams <RW...@up.com> wrote:
>
> > Whether the reasons are valid or not irrelevant. I only passed along what
> > I have heard; don't necessarily agree with the rationales. As I said, I
> > was not consulted (and probably never will be).
> >
> >
> >
> >
> > From: Paul Bors <pa...@bors.ws>
> > To: "users@wicket.apache.org" <us...@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.
> >
> > 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 from Wicket 1.3.x to 6.x
> by
> > myself in under 2 weeks simply by following the migration tutorials one
> by
> > one.
> >
> > 2) Cost of tranning new developers
> > Wicket itself is model much after the Java's Swing and it promotes
> > fast
> > adaptation for new developers (they teach Swing in college). Perhaps the
> > new staff should consider spending 1 to 2 weeks reading one of the many
> > books avaialble on Wicket, see:
> > http://wicket.apache.org/learn/books/
> >
> > I spent a good 3-4 weeks reading over Andreas' free guide whcih took so
> > long because I was reading it a chpater a day on the subway ride to work
> > while at the same time proof reading his new material. You can print the
> > free guide via:
> > http://wicket.apache.org/start/userguide.html
> >
> > I don't know AngualrJS too much as I never worked with it. To me it looks
> > like another JS framework out there in the mixture of many that can very
> > easily be integrated with Wicket. Perhaps you should suggest that to your
> > upper management.
> >
> > Anyhow, that's my two cents.
> >
> >
> > On Fri, Jan 3, 2014 at 12:12 PM, Richard W. Adams <RW...@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 considering whether to make the leap from
> > > Wicket 1.4.17 to 6.x.
> > >
> > > 2. A perception of excessive cost in training new developers to use
> > > Wicket. I myself am fairly comfortable with Wicket now (after 2 years
> > > experience), but have to admit the leaning curve was pretty steep.
> > >
> > >
> > >
> > >
> > > From: Ernesto Reinaldo Barreiro <re...@gmail.com>
> > > To: users@wicket.apache.org
> > > Date: 01/03/2014 10:58 AM
> > > Subject: Re: Converting Wicket to AngularJS/Spring MVC
> > >
> > >
> > >
> > > 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
> > >
> > >
> > >
> > > **
> > >
> > > This email and any attachments may contain information that is
> > > confidential and/or privileged for the sole use of the intended
> > recipient.
> > > Any use, review, disclosure, copying, distribution or reliance by
> > others,
> > > and any forwarding of this email or its contents, without the express
> > > permission of the sender is strictly prohibited by law. If you are not
> > the
> > > intended recipient, please contact the sender immediately, delete the
> > > e-mail and destroy all copies.
> > > **
> > >
> >
> >
> >
> > **
> >
> > This email and any attachments may contain information that is
> > confidential and/or privileged for the sole use of the intended
> recipient.
> > Any use, review, disclosure, copying, distribution or reliance by
> others,
> > and any forwarding of this email or its contents, without the express
> > permission of the sender is strictly prohibited by law. If you are not
> the
> > intended recipient, please contact the sender immediately, delete the
> > e-mail and destroy all copies.
> > **
> >
>
Re: Rationale for Converting to AngularJS/Spring MVC
Posted by Martin Grigorov <mg...@apache.org>.
Make some noise about this (stupid) decision and when the higher management
realize the mistake they made they will ask you ;-)
Martin Grigorov
Wicket Training and Consulting
On Mon, Jan 6, 2014 at 3:11 PM, Richard W. Adams <RW...@up.com> wrote:
> Whether the reasons are valid or not irrelevant. I only passed along what
> I have heard; don't necessarily agree with the rationales. As I said, I
> was not consulted (and probably never will be).
>
>
>
>
> From: Paul Bors <pa...@bors.ws>
> To: "users@wicket.apache.org" <us...@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.
>
> 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 from Wicket 1.3.x to 6.x by
> myself in under 2 weeks simply by following the migration tutorials one by
> one.
>
> 2) Cost of tranning new developers
> Wicket itself is model much after the Java's Swing and it promotes
> fast
> adaptation for new developers (they teach Swing in college). Perhaps the
> new staff should consider spending 1 to 2 weeks reading one of the many
> books avaialble on Wicket, see:
> http://wicket.apache.org/learn/books/
>
> I spent a good 3-4 weeks reading over Andreas' free guide whcih took so
> long because I was reading it a chpater a day on the subway ride to work
> while at the same time proof reading his new material. You can print the
> free guide via:
> http://wicket.apache.org/start/userguide.html
>
> I don't know AngualrJS too much as I never worked with it. To me it looks
> like another JS framework out there in the mixture of many that can very
> easily be integrated with Wicket. Perhaps you should suggest that to your
> upper management.
>
> Anyhow, that's my two cents.
>
>
> On Fri, Jan 3, 2014 at 12:12 PM, Richard W. Adams <RW...@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 considering whether to make the leap from
> > Wicket 1.4.17 to 6.x.
> >
> > 2. A perception of excessive cost in training new developers to use
> > Wicket. I myself am fairly comfortable with Wicket now (after 2 years
> > experience), but have to admit the leaning curve was pretty steep.
> >
> >
> >
> >
> > From: Ernesto Reinaldo Barreiro <re...@gmail.com>
> > To: users@wicket.apache.org
> > Date: 01/03/2014 10:58 AM
> > Subject: Re: Converting Wicket to AngularJS/Spring MVC
> >
> >
> >
> > 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
> >
> >
> >
> > **
> >
> > This email and any attachments may contain information that is
> > confidential and/or privileged for the sole use of the intended
> recipient.
> > Any use, review, disclosure, copying, distribution or reliance by
> others,
> > and any forwarding of this email or its contents, without the express
> > permission of the sender is strictly prohibited by law. If you are not
> the
> > intended recipient, please contact the sender immediately, delete the
> > e-mail and destroy all copies.
> > **
> >
>
>
>
> **
>
> This email and any attachments may contain information that is
> confidential and/or privileged for the sole use of the intended recipient.
> Any use, review, disclosure, copying, distribution or reliance by others,
> and any forwarding of this email or its contents, without the express
> permission of the sender is strictly prohibited by law. If you are not the
> intended recipient, please contact the sender immediately, delete the
> e-mail and destroy all copies.
> **
>
Re: Rationale for Converting to AngularJS/Spring MVC
Posted by "Richard W. Adams" <RW...@UP.COM>.
Whether the reasons are valid or not irrelevant. I only passed along what
I have heard; don't necessarily agree with the rationales. As I said, I
was not consulted (and probably never will be).
From: Paul Bors <pa...@bors.ws>
To: "users@wicket.apache.org" <us...@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.
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 from Wicket 1.3.x to 6.x by
myself in under 2 weeks simply by following the migration tutorials one by
one.
2) Cost of tranning new developers
Wicket itself is model much after the Java's Swing and it promotes
fast
adaptation for new developers (they teach Swing in college). Perhaps the
new staff should consider spending 1 to 2 weeks reading one of the many
books avaialble on Wicket, see:
http://wicket.apache.org/learn/books/
I spent a good 3-4 weeks reading over Andreas' free guide whcih took so
long because I was reading it a chpater a day on the subway ride to work
while at the same time proof reading his new material. You can print the
free guide via:
http://wicket.apache.org/start/userguide.html
I don't know AngualrJS too much as I never worked with it. To me it looks
like another JS framework out there in the mixture of many that can very
easily be integrated with Wicket. Perhaps you should suggest that to your
upper management.
Anyhow, that's my two cents.
On Fri, Jan 3, 2014 at 12:12 PM, Richard W. Adams <RW...@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 considering whether to make the leap from
> Wicket 1.4.17 to 6.x.
>
> 2. A perception of excessive cost in training new developers to use
> Wicket. I myself am fairly comfortable with Wicket now (after 2 years
> experience), but have to admit the leaning curve was pretty steep.
>
>
>
>
> From: Ernesto Reinaldo Barreiro <re...@gmail.com>
> To: users@wicket.apache.org
> Date: 01/03/2014 10:58 AM
> Subject: Re: Converting Wicket to AngularJS/Spring MVC
>
>
>
> 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
>
>
>
> **
>
> This email and any attachments may contain information that is
> confidential and/or privileged for the sole use of the intended
recipient.
> Any use, review, disclosure, copying, distribution or reliance by
others,
> and any forwarding of this email or its contents, without the express
> permission of the sender is strictly prohibited by law. If you are not
the
> intended recipient, please contact the sender immediately, delete the
> e-mail and destroy all copies.
> **
>
**
This email and any attachments may contain information that is confidential and/or privileged for the sole use of the intended recipient. Any use, review, disclosure, copying, distribution or reliance by others, and any forwarding of this email or its contents, without the express permission of the sender is strictly prohibited by law. If you are not the intended recipient, please contact the sender immediately, delete the e-mail and destroy all copies.
**
Re: Rationale for Converting to AngularJS/Spring MVC
Posted by Paul Bors <pa...@bors.ws>.
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 from Wicket 1.3.x to 6.x by
myself in under 2 weeks simply by following the migration tutorials one by
one.
2) Cost of tranning new developers
Wicket itself is model much after the Java's Swing and it promotes fast
adaptation for new developers (they teach Swing in college). Perhaps the
new staff should consider spending 1 to 2 weeks reading one of the many
books avaialble on Wicket, see:
http://wicket.apache.org/learn/books/
I spent a good 3-4 weeks reading over Andreas' free guide whcih took so
long because I was reading it a chpater a day on the subway ride to work
while at the same time proof reading his new material. You can print the
free guide via:
http://wicket.apache.org/start/userguide.html
I don't know AngualrJS too much as I never worked with it. To me it looks
like another JS framework out there in the mixture of many that can very
easily be integrated with Wicket. Perhaps you should suggest that to your
upper management.
Anyhow, that's my two cents.
On Fri, Jan 3, 2014 at 12:12 PM, Richard W. Adams <RW...@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 considering whether to make the leap from
> Wicket 1.4.17 to 6.x.
>
> 2. A perception of excessive cost in training new developers to use
> Wicket. I myself am fairly comfortable with Wicket now (after 2 years
> experience), but have to admit the leaning curve was pretty steep.
>
>
>
>
> From: Ernesto Reinaldo Barreiro <re...@gmail.com>
> To: users@wicket.apache.org
> Date: 01/03/2014 10:58 AM
> Subject: Re: Converting Wicket to AngularJS/Spring MVC
>
>
>
> 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
>
>
>
> **
>
> This email and any attachments may contain information that is
> confidential and/or privileged for the sole use of the intended recipient.
> Any use, review, disclosure, copying, distribution or reliance by others,
> and any forwarding of this email or its contents, without the express
> permission of the sender is strictly prohibited by law. If you are not the
> intended recipient, please contact the sender immediately, delete the
> e-mail and destroy all copies.
> **
>
Rationale for Converting to AngularJS/Spring MVC
Posted by "Richard W. Adams" <RW...@UP.COM>.
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 excessive cost in training new developers to use
Wicket. I myself am fairly comfortable with Wicket now (after 2 years
experience), but have to admit the leaning curve was pretty steep.
From: Ernesto Reinaldo Barreiro <re...@gmail.com>
To: users@wicket.apache.org
Date: 01/03/2014 10:58 AM
Subject: Re: Converting Wicket to AngularJS/Spring MVC
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
**
This email and any attachments may contain information that is confidential and/or privileged for the sole use of the intended recipient. Any use, review, disclosure, copying, distribution or reliance by others, and any forwarding of this email or its contents, without the express permission of the sender is strictly prohibited by law. If you are not the intended recipient, please contact the sender immediately, delete the e-mail and destroy all copies.
**
Re: Converting Wicket to AngularJS/Spring MVC
Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
Hi,
On Fri, Jan 3, 2014 at 1:54 PM, Richard W. Adams <RW...@up.com> 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
Re: Converting Wicket to AngularJS/Spring MVC
Posted by Andrea Del Bene <an...@gmail.com>.
Hi,
I don't have a direct experience migrating a Wicket app to a
AngularJS/Spring MVCC, but in my current project we have a Wicket
application with a Spring MVC part for REST APIs. We are using to
different servlet filters, one for the Wicket part and one for Spring
MVC. In this way you can use both the two frameworks, but I don't know
how you could make them "communicate" (i.e. Wicket pages with Spring
controllers).
I guess you want to create some kind of REST application with Spring MVC
with Angualr on client side to invoke REST APIs...the best solution
would be to continue using Wicket :-) and to implement REST APIs with
the WicketStuff module for REST applications
(https://github.com/wicketstuff/core/tree/master/jdk-1.6-parent/wicketstuff-restannotations-parent).
> 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?
>
> 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!)
>
> **
>
> This email and any attachments may contain information that is confidential and/or privileged for the sole use of the intended recipient. Any use, review, disclosure, copying, distribution or reliance by others, and any forwarding of this email or its contents, without the express permission of the sender is strictly prohibited by law. If you are not the intended recipient, please contact the sender immediately, delete the e-mail and destroy all copies.
> **
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org