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 is not compiled with the build.
It is possible, although very convoluted and clumsy, to change the build process to pick up source files generated by my generator and include them in the build path so they can be compiled and available at runtime. I have instead created a separate class to generate my java source code. This class is used by the generator to generate the java source to be cross-compiled by GWT. The same class is then used by my application to dynamically generate and load these java classes into the VM. They are then available at runtime and all seems to be working fine. Thank you again for your help and if anyone needs more information about this workaround I will be happy to send it to them. On Sep 22, 2:20 am, Martin Söderström <martin.k.soderst...@gmail.com> wrote: > 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 -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
