going pure GWT can never be wrong, if u want to play safe, make ur server
talking only JSON/rest not GWT-RPC
by that u can later decided to throw away the presentation layer if another
promising client framework should become popular
so far, java's tooling system is too good to give up ...
So it would have been totally safe to bet the farm on EJB2.1 because that
is here for good? CORBA inside JSE!
On Friday, December 13, 2013 1:35:27 AM UTC, Willie Slepecki wrote:
>
> My team just wrapped up an evaluation comparing gwt to jsf to be used in a
> new series of applications we are pl
Willie,
7-10 years is an eternity, even in my company we don't stick so long on one
technology. With proper design you can make sure that the business logic
can survive the technology you used. Nothing guarantees that JSF will
survive and trive for so long. Look at SWING, AWT, Struts, it used to b
On Friday, December 13, 2013 2:35:27 AM UTC+1, Willie Slepecki wrote:
>
> My team just wrapped up an evaluation comparing gwt to jsf to be used in a
> new series of applications we are planning. My team chose pure gwt over
> jsf and vaadin for a variety of reasons.
>
> Our problem is two of
My team just wrapped up an evaluation comparing gwt to jsf to be used in a new
series of applications we are planning. My team chose pure gwt over jsf and
vaadin for a variety of reasons.
Our problem is two of the primary decision makers are convinced that gwt is
going to dilute and within 7
