Thank you Martin.
I think I have found a fix. GWT seems to generate the java source only
for the purpose of cross-compiling it into javascript and then
discards the generated java files. There is a compiler option to keep
the generated java code in a specific folder but the resulting .java
file
Farid,
FYI: my team stopped progress on this project before I had the chance to supply
Chris the code for the generated class and gwt.rpc, so we never actually sorted
this out. Maybe Chris would still be interested in seeing your code now
instead to have a look at what's going on.
/Martin
--
Hello Martin and Chris,
I was wondering if there is any final answer to this issue. I happen to have
the same problem whereby I cannot send classes generated by my generator
through GWT RPC. The GWT RPC generator does not seem to be able to find the
source for my generated class.
Let me know
Chris,
Thanks for trying to help me with this. As for your questions, I'm not
sure I understand the second one, but I'll exemplify better what my
code is doing:
First there is a listener interface:
public interface TestMessageListener {
void messageReceived(String message);
}
Then
My comments/questions inline:
The generated class extends this AbstractRpcObserver (and is thereby
Serializable) and implements the TestMessageListener interface. An
instance of the generated class is used as argument in the
addMessageListener method invoction in the RPC service.
If I
