Hi!
If I'd start the project today, I'd just use plain REST / JSON for both the
desktop and mobile versions.
Ok, but how can you do REST/JSON with a GWT application?
Would you replace the RPC calls with REST requests, using a servlet or what?
Thanks
Magnus
--
You received this message
Here is what I would do :
1) refactor your business logic (which usually returns a Serializeable object)
out of the GWT RemoteServeiceServelt,
2) Create some normal Java servelet with the API style of your
choosing, REST or not.
3) Call your business logic from both places, GWT just return the
1) refactor your business logic (which usually returns a Serializeable
object)
out of the GWT RemoteServeiceServelt,
http://www.gwtproject.org/javadoc/latest/com/google/gwt/user/server/rpc/RemoteServiceServlet.html#RemoteServiceServlet(java.lang.Object)
GWT-RPC servlets already have the
Ok, but how can you do REST/JSON with a GWT application?
For me RestEasy + Errai JAX-RS is working perfectly fine.
On Wednesday, December 3, 2014 10:16:23 AM UTC-8, Magnus wrote:
Hi!
If I'd start the project today, I'd just use plain REST / JSON for both
the desktop and mobile versions.
ok, but this leads me to the question, why we don't use REST/JSON right
from the beginning?
Isn't it a potential option for nearly any web application today to be
complemented by a mobile version some day?
I work in a large project which started in 2008, but was not full time back
ok, but this leads me to the question, why we don't use REST/JSON right
from the beginning?
At the beginning of a project you usually know what you want to do. So if
you want native clients for different platforms then you will start with
some sort of REST/JSON or protobuff/thrift/...
Ok, I have to sort some ideas...
- Given an existing GWT application: Can you add a REST interface so
that you can access the services with a new Android app?
How do you do this? Would it be a good idea to add a servlet that
handles the REST based requests?
- What about an
Hi,
ok, but this leads me to the question, why we don't use REST/JSON right
from the beginning?
Isn't it a potential option for nearly any web application today to be
complemented by a mobile version some day?
Are there any tutorials out there for building web apps based on GWT with
mobile
ok, but this leads me to the question, why we don't use REST/JSON right
from the beginning?
At the beginning of a project you usually know what you want to do. So if
you want native clients for different platforms then you will start with
some sort of REST/JSON or protobuff/thrift/...
Personally I would not use GWT-RPC then because you would have to port the
client side serialization/deserialization of GWT-RPC to Android and maybe
in the future even iOS if you want a native iOS app as well. So you should
stick to a more standard serialization that can easily be
Hi,
I have looked to both of them, and I found that they focus on the client
side GUI.
But the GUI is something I would like to do with the native Android SDK.
What I would like to do is access the data on my tomcat server, just as I
do it with GWT client applications.
Assume a GWT chess app
Check them out:
- mGWT
- GWTP with different device bindings (mobile/tablet/desktop)
-J
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Hi,
assume a normal GWT app, with a server side part and a client side part,
which communicate over RPC.
Can you add a mobile version with minimal effort, i. e.:
- reuse the same server side part and the shared classes
- replace the client side part
- keep everything unique, without
13 matches
Mail list logo
