I see. Interesting. In that case the easiest way I can think of would be to forget the strong name, name the RPC file some arbitrary name that you copy the generated file to after the GWT compile, and then use that name with SerializationPolicyLoader to get your policy instance.
But yeah, like you said, there are a lot of ways you can do it, including implementing your own policy. I've never heard of doing this before so I can't really comment on best practice. Maybe someone else can help you out more. On Feb 3, 1:50 pm, "[email protected]" <[email protected]> wrote: > Just to clarify - I'm doing this as part of a regular page request > that bootstraps part of my application, not in response to a GWT RPC > call. So, for example, the client goes to the Foo page and my app > returns the Foo GWT gadget in the page along with all of the data it > needs to start up. > > So there would be no client request to parse for the strong name. I > guess I could catch the strong name when it's sent from as part of the > nocache request and put it into the session or something... but that > is a bit ugly. > > What I was hoping for is a way to get the strong name statically from > some compiled code or some clean way to find the file as part of my > build process. > > I can think of many hacks to fix it... or maybe building a linker, but > all seem wrong. > > 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 -~----------~----~----~----~------~----~------~--~---
