Hi,
I agree with you not to use GWT-RPC for anything else then the gui-
client.
It is very likely that an other access source have special demands
which collides with GWT-RPC.
(Maybe a different kind of authentication)
Stefan Bachert
http://gwtworld.de
On 28 Mai, 18:10, "mikedshaf...@gmail.com
Thanks Sri, Mike! Yes, it seems that a more transparent & light-weight
protocol would be better in the long term.
MG
On May 28, 12:10 pm, "mikedshaf...@gmail.com"
wrote:
> Another, more recommended method is to isolate the business process
> away from the GWT RPC. So you have a stand alone "mid
Another, more recommended method is to isolate the business process
away from the GWT RPC. So you have a stand alone "middle-tier" that
you communicate with via GWT-RPC and Swing Clients and whatever else
you want to do. Don't try to reuse GWT-RPCgo around it. It's a
better design...
On May
Having said that, I wouldn't build a production app that relies on the
library.
If you really want to develop your services for multiple clients, I'd
recommend staying away from GWT RPC. JSON is well suited for the browser,
while XML is better suited for a Swing application. If you build your
serv
See http://www.gdevelop.com/w/blog/2010/01/10/testing-gwt-rpc-services/.
That's the best solution that's out there at the moment.
--Sri
On 28 May 2010 20:36, ussuri wrote:
> Hello! I know that the question has been asked several times, but the
> last discussion I was able to find dates back to
Hello! I know that the question has been asked several times, but the
last discussion I was able to find dates back to 2009, so I'll ask the
question again:
Can I _easily_ call GWT-RPC server side from a pure java client
application? If not, is the ability on the roadmap? What are the best
alterna
