The modules use the super-source directive to state where the override class are stored. These still need to be Java and compilable in java, the gwt compiler sort of replaces references of the real class with this override class when referenced on the clientside.
On Mar 12, 8:37 am, Olostan <[email protected]> wrote: > Result of GWT compiling is JavaScript code. So to convert your Java > code to JavaScript GWT need those classes if you use them. That was > 'why'. How? I am not sure, but as it is 'emulation' library, these > classes are not extracted, but or hard-coded in JavaScript directly or > wrote in Java but especially for GWT. > > Best practice depends on your project purpose. General ways are > described in GWT manual > (lookhttp://code.google.com/intl/uk-UA/webtoolkit/doc/latest/DevGuideServe... > ) > > Good luck! > > On 11 Бер, 10:51, mousedolly2002 <[email protected]> wrote: > > > > > I have worked with GWT for a while. > > And I want to know why and how does GWT extract these subset of the > > core Java class libraries ? > > ashttp://code.google.com/intl/ja/webtoolkit/doc/latest/RefJreEmulation.... > > anyone can tell me. > > > And, I want to know if there is any best practice or rules about how > > split code between server side and client side. > > > thanks a lot! > > OI will appreciate your reply. -- 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.
