We have multiple modules that are coming from the different providers, there is no way to compile them together as well as GWT compile time grows exponentially, everything works great in PRETTY mode only and there are some method not found exceptions when using Obfuscated or Detailed mode.
On Aug 25, 1:22 pm, Sumit Chandel <[email protected]> wrote: > Hi Vlad, > I actually misspoke in my previous post - including the two independently > compiled modules in your host HTML page should work, although the ideal > would still be to combine the two to avoid the redundant boilerplate code > from being downloaded a second time and to take advantage of optimizations > that come from a monolithic compilation over one codebase. > > However, if you really need to work with these modules as two separate > entities, could you elaborate a little more on the error message you receive > or any errors reported in the JavaScript console when using DETAILED or OBF > compiled output? > > Hope that helps, > -Sumit Chandel > > > > On Mon, Aug 24, 2009 at 12:27 PM, Vladimir <[email protected]> wrote: > > > Thanks for your reply, I have at least two modules both using GWT-Ext, > > i include them on the same hosting page with two lines as > > <script type="text/javascript" src="/com.test.Modeule1.nocache.js"></ > > script> > > <script type="text/javascript" src="/com.test.Modeule2.nocache.js"></ > > script> > > > everything works fine in the PRETTY mode but doesn't in the Detailed > > or Obfuscated it also works fine in hosted mode as well. I world > > understand if OBF fails but it fails in both OBD and Detailed and no > > in Pretty. > > > --Vlad > > > On Aug 21, 1:39 pm, Sumit Chandel <[email protected]> wrote: > > > Hi Vlad, > > > If I understand correctly, you have one GWT module built with GWT itself, > > > and another module built with GWT-Ext, and you're adding both modules to > > the > > > same page? If that's the case, I can see how this error could occur, but > > > it's probably not a good idea to develop two independent modules and > > include > > > them in the same page anyway. > > > > You should consider reusing one module in the other, or if that's not > > > possible because of library incompatibilities between GWT and GWT-Ext, > > > switching to only one of the two solutions and creating one module that > > can > > > be compiled monolithically. That would not only correct the issue you're > > > facing now, but would also lead to much smaller JavaScript code and a > > much > > > snappier application. > > > > Hope that helps, > > > -Sumit Chandel > > > > On Tue, Aug 18, 2009 at 6:44 AM, Vlad <[email protected]> wrote: > > > > > When putting multiple GWT modules on the html host page that use gwt- > > > > ext library there is JavaScript error and only in the OBFuscated mode. > > > > Everything works just fine in the PRETTY mode. Most likely the error > > > > is caused by the name collision in the obfuscated mode when method aa1 > > > > () from one module collides with the same obfuscated name from the > > > > second one. Basically when first module executes some method there is > > > > an error and stack trace reference to the HTML file from the different > > > > module. > > > > > Is there any way to specify some range for JavaScript method names > > > > when compiling in the OBFuscated mode via linker etc. > > > > > Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
