My timing is probably bad again since you are in the last sprint to delivering GWT 2.7. (Looking forward to it!) Any chance that this bug will ever get resolved in some way or another ? http://code.google.com/p/google-web-toolkit/issues/detail?id=1888 It is about the possibility to use GWT RPC services in an OSGI environment. While the trick with setting the context classloader works in most cases, there are some cases (I am trying to figure out the exact cause) that it does not seem to help. I have some seemingly "random" classes that fail to load correctly. When I move the class to a different package (in the same bundle!) then suddenly it works. The bug is marked as AssumedStale... but it is still very much a problem. I searched on StackOverflow and other sites but nowhere did I find a complete solution. The main gist seems to be that we need some way to instruct the GWT servlet to use a custom classloader instead of the context classloader to find the RPC request/response objects. Setting a custom ContextClassLoader does not seem to fix everything so there must be some places where the wrong classloader is being used.
-- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/0d92c5f9-2314-443c-a5b1-3d3e5631d4c3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
