On Feb 2, 7:45 pm, Dan Ox <[email protected]> wrote:
> Are you decoding the request by hand?
No. I'm simply encoding an object on the server side and stuffing it
into the page using RPC.encodeResponseForSuccess(). Then on the
client side I am pulling it out and decoding it with a
SerializationStreamFactory. (Strictly Server->Client)
> The SerializationPolicyProvider implementation defines the method:
> getSerializationPolicy(String, String);
>
> this provides both the module name and the strong name which you can
> then easily use to read in the rpc file and create a
> StandardSerialisationPolicy.
Yes, but that is my problem. I do not know the strong name. So I
have been manually copying the compiled .gwt.rpc file to a known name
and then loading it with SerializationPolicyLoader in order to use the
encode API.
Maybe I'm missing something terribly obvious here. Is there some
procedural way to determine the strong name at run time? And if so
are you suggesting that I then send that name to the server with each
request as part of my API?
thanks,
Pat
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
