Under 1.4 we used to use the old typeArgs for returning a List
When we moved to 1.5 we went to parameterized types, as recommended
for Lists.
All of a sudden, a method on an RPC service I was writing today that
returned a List failed:
public List<DriverlibRepositoryDef> getRepositories()
(the specifics of what this do don't matter)
I knew we used a parameterized List return in another RPC service we
had
public List<ServerEvent> getEvents(long firstId, int maxEvents)
throws Exception;
so couldn't figure why this failed.
And then I noticed - the original code that worked also now failed.
Digging some more, I realised these are the only 2 methods in our RPC
services that return Lists.
Odder still - if I change the new one to return an Array - both start
working.
I can't fathom why, but it seems when using a parameterised List as a
return object, it seems to get lost if I have more than 1 method doing
so.
-- Rob
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
