On 9ζ28ζ₯, εεΎ4:04, Asko Saura <[email protected]> wrote: > I compile the server versions into .class files. Then I include > a .gwt.xml file describing them as a gwt module and put the .class > files and the client .java files in a jar file.
> I compile the server versions into .class files. Then I include > a .gwt.xml file describing them as a gwt module and put the .class > files and the client .java files in a jar file. Why don't you use the super-source? For example === src/xxx/yyy/Sample.gwt.xml src/xxx/yyy/server/SampleDto.java super/xxx/yyy/translatable/xxx/yyy/server/SampleDto.java The "src" is source directory. The "super" is normal directory. For both "SampleDto.java", the package declaration is "xxx.yyy.server". Sample.gwt.xml with the following contents: <source path="client" /> <super-source path="translatable" /> then On the server, "xxx.yyy.server.SampleDto.java" is used. On the client, "xxx.yyy.translatable.xxx.yyy.server.SampleDto.java" is used. === The super-source brings me the code separation between the client and the server. But I think "GWT people" don't want this, too. I really hope an @ServerOnly type annotation will be supported. -- buffeirngs --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
