Re: java.lang.IllegalArgumentException: Unknown proxy type

2011-08-18 Thread PTed
@ExtraTypes works. But I have multiple request calls. So @ExtraTypes can't be used. Also the Proxies don't extends. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit

Re: java.lang.IllegalArgumentException: Unknown proxy type

2011-08-17 Thread Andigator
This happens for me when I am extending EntityProxy directly for proxyA and proxyB and try to append requestA to requestB. @ExtraTypes won't fix it in my case. Ideas? On Aug 16, 3:44 pm, Y2i yur...@gmail.com wrote: filed an

Re: java.lang.IllegalArgumentException: Unknown proxy type

2011-08-17 Thread Y2i
Have you tried to use @ExtraTypes on an interface that extends RequestFactory? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/2qFWHzw8pTsJ. To

Re: java.lang.IllegalArgumentException: Unknown proxy type

2011-08-16 Thread Y2i
filed an issue: http://code.google.com/p/google-web-toolkit/issues/detail?id=6699 -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/Au8I9VHZkAQJ.

Re: java.lang.IllegalArgumentException: Unknown proxy type

2011-08-04 Thread Y2i
bumping up... -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/I5nN_KnYVc4J. To post to this group, send email to

java.lang.IllegalArgumentException: Unknown proxy type

2011-08-03 Thread Y2i
() callback is called fine. When queryCountOfP() accepts an instance of PB, the failure occurs: java.lang.IllegalArgumentException: Unknown proxy type PB The server receives the call, the argument type of the service method is correct (B), but after returning to the client the following method throws