Progress ... of a sort. I think this is something to do with the way we package our GWT service handlers into OSGi bundles.
I don't really understand how the GWT serializer and proxy code works ... but ... the thing that is different about this new service handler class is that it exists in a different package and bundle to our normal GWT service handler classes. If I move it into our "xx.xx.xx.server" package, bingo, it all starts working. My guess is the reason comes down to 1 of 2 things: - the GWT compiler wants to scan all xxxServiceImpl classes that use RemoteServiceServlet to deliver an RPC service as part of it's proxy generation - there is some package/class resolution failing which causes the seriallizer code to fail The latter is very common in OSGi, but I don't see any errors to suggest that happens in this case. What's strange is that this only seems to effect the two services returning List<E> types - and the class in a different package and bundle breaks both of them. That kind of suggests to me that there's some generic ArrayList<E> serializer being used for both these cases, and because one of the services exists in a different package that wasn't scanned by the GWT compiler, it somehow breaks both cases. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
