Thanks Thomas. This insight is extremely helpful.
On Tuesday, April 12, 2016 at 3:41:23 AM UTC-7, Thomas Broyer wrote:
>
>
>
> On Monday, April 11, 2016 at 10:59:34 PM UTC+2, Paul Mazzuca wrote:
>>
>> RestyGWT is enticing considering how well it decouples the client and the
>> server.
On Monday, April 11, 2016 at 10:59:34 PM UTC+2, Paul Mazzuca wrote:
>
> RestyGWT is enticing considering how well it decouples the client and the
> server. Thanks. I am still curious about a community (I guess I mean
> steering committee) recommendation though, especially if there are plans
I'm using GWTP Rest Dispatch. It works almost the same as RestyGWT but it
depends on GWT-Jackson for serialisation/deserialisation. GWT Jackson
supports more features of Jackson than RestyGWT.
On Tue, Apr 12, 2016 at 12:16 AM Vassilis Virvilis
wrote:
> I am using GWT +
I am using GWT + RestyGWT + CXF (server side for REST service definition).
It is just a testament on your comment on how well RestyGWT decouples
client and server. Furthermore I am extremely happy with the RestyGWT
developers.and their way to run the project..
For me RestyGWT is the answer but I
RestyGWT is enticing considering how well it decouples the client and the
server. Thanks. I am still curious about a community (I guess I mean
steering committee) recommendation though, especially if there are plans to
update certain code like the RequestFactory. Even if the steering
I'm using GWT + RestyGWT + Jersey (server-side for REST service definition)
in my latest GWT app. I intend to use those tools + Objectify + JDO? for a
new GWT-AppEngine app. Not sure about how it will work as I'm yet to get
started with this toolchain, but I remember David Chandler writing
Is GWT + RequestFactory + Google App Engine + JDO still considered a best
practice (as suggested by the GWT docs), or is there a recommended
alternative, assuming I would like to use GWT with AppEngine cloud
datastore?
I have used this combination for a while, however the code is slowly