How can I call a GWT RPC method on a server from a non GWT (but Java) gapplication?
The Java implementation in GWT of the RPC protocol in the packages com.google.gwt.user.serve" rel="nofollow">com.google.gwt.user.server. Rpc and com.google.gwt.user.serve" rel="nofollow">com.google.gwt.user.server.rpc. Impl unfortunately only covers deserialization of requests and serialization of responses.
The real work is done in the classes ServerSerializationStreamReader and ServerSerializationStreamWriter (each appr. 750 lines of code) To implement a client, you obviously need to serialze the request and deserialize the response, but since there's no documentation available for the protocol and AFAIK no Java client implementations available, you probably would have to reverse-engineer the (de)serialization classes and write your own code to do everything "the other way around You can find some high-level info about the protocol here.
The Java implementation in GWT of the RPC protocol in the packages com.google.gwt.user.serve" rel="nofollow">com.google.gwt.user.server. Rpc and com.google.gwt.user.serve" rel="nofollow">com.google.gwt.user.server.rpc. Impl unfortunately only covers deserialization of requests and serialization of responses.
The real work is done in the classes ServerSerializationStreamReader and ServerSerializationStreamWriter (each appr. 750 lines of code). To implement a client, you obviously need to serialze the request and deserialize the response, but since there's no documentation available for the protocol and AFAIK no Java client implementations available, you probably would have to reverse-engineer the (de)serialization classes and write your own code to do everything "the other way around".
You can find some high-level info about the protocol here.
GWT SyncProxy allows you to access GWT RPC services (e. G methods) from pure Java (not JSNI) code. See gdevelop.com/w/blog/2010/01/10/testing-g... for details.
Unfortunately, I think jarnbjo is right about having to reimplement the browser's half of the RPC mechanism. Alternately, if you end up having to write a REST interface for remote clients, you can switch your GWT app away from the RPCs and use the REST interface there too, and share your client library between the external clients and the GWT's client-side interface.
You can find what you search in this article about GwtRpcCommLayer : googlewebtoolkit.blogspot.com/2010/07/gw....
The Java implementation in GWT of the RPC protocol in the packages com.google.gwt.user.server. Rpc and com.google.gwt.user.server.rpc. Impl unfortunately only covers deserialization of requests and serialization of responses.
The real work is done in the classes ServerSerializationStreamReader and ServerSerializationStreamWriter (each appr. 750 lines of code).
GWT SyncProxy allows you to access GWT RPC services (e. G methods) from pure Java (not JSNI) code.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.