> Just... beware. This makes you INCOMPATIBLE WITH THE FUTURE. Should > a bug fix or breaking change get released, and you've got super-source > everywhere, you're gonna be super-sad.
So what's the point in recommending people to copy-paste whole classes ? None, so you really shouldn't be giving the impression that because it's possible you should do it. Don't copy-paste whole classes, its very very bad practice. Thomas' solution is the way to go if you really need to modify the class behaviour or access protected methods. Cheers, Salvador On 13 mai, 14:59, Alyxandor <[email protected]> wrote: > gwt uses an option called super-source to let you literally replace > one class with another. It's dangerous mojo and potentially > dangerous, but you basically make a seperate module whereever you want > {com.example for now}, and in that whatever.gwt.xml, you put: > > <?xml version="1.0" encoding="UTF-8"?> > <module> > <super-source path="whatever" /> > </module> > > THEN, if you want to override > com.google.gwt.http.client.RequestBuilder, you can copy all the code > in RequestBuilder, and put it at com/example/whatever/com/google/gwt/ > http/client/RequestBuilder and then just include com.example.whatever. > > Just... beware. This makes you INCOMPATIBLE WITH THE FUTURE. Should > a bug fix or breaking change get released, and you've got super-source > everywhere, you're gonna be super-sad. > > CHEERS! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
