Another option is that the annotations are probably not necessary in the client side, so you might be able to do some post-processing after generating with JAXB to remove them. I imagine they're needed server-side, so you'd have to use super-source in your gwt.xml to make it use the cleaned up versions in the client.
The .java files really are needed for the gwt compilation. I think the main problem is that the .class files lose a lot of the information that was in the source files, and so it's not possible to do the same amount of optimization. On 01/04/11 13:09, Michele Rossi wrote:
I guess one way could be to somehow get the source code for the annotations too, and re-build them into a GWT module. I am talking about a hack - you wouldn't change the class names or the package names.. Maybe I will try when I get a chance - if it works I will post it to the group. I am thinking that it seems really un-necessary to have the source code for every single line of translatable code. Bytecode is readable enough, and there are libraries to read it. Maybe something to hope for in the next GWT releases (unless I am missing a really obvious reason why having the .java files is absolutely necessary). thanks, Michele -- 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.
-- 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.
