AFAIK there is no a standard way to say the compiler which classes/methods leave in your js code except from using them, apart from obfuscate names, the compiler will remove any single method you dont use in your code, and even it could inline certain method calls.
Said that, I think a way to control that those methods remain in the compiled stuff although you dont use them is by using the gwt-exporter library as you point in your email. It will generate auxiliary code to expose the api wich will reference all the annotated methods and classes guaranteeing you that all that stuff will be in your compiled js modules. But what it isn't possible is that both separate GWT modules generate the same names and references inside the gwt classes, so although gwt-exporter allows exported methods which returns gwt objects, those objects would not be usable across modules. In summary, what I would do is to use gwt-exporter in both modules to generate a js api of certain parts of your app, and consume that js api via jsni like any other external js library. - Manolo On Mon, Oct 15, 2012 at 12:06 PM, erik <m8r-y3l...@chammy.info> wrote: > Hey everyone, > > I'm currently researching ways to implement communication between two > separate GWT modules within a host page. I know it's generally possible > using JSNI, exporting of Java functions (via gwt-exporter or manually) and > overlay types (JavascriptObject and so on). > However, due to project circumstances I need to pass java objects between > those modules that do NOT extend JavascriptObject. The reason is that I > cannot introduce a GWT dependency into an otherwise non-GWT code base which > is used for one of these modules. So far I only added classes around the > actual code base that implement GWT-specific behaviour (mainly an > EntryPoint class) and delegate to the underlying functionality. > > By testing I found out that I can pass custom java objects between my > modules if I make sure that the necessary methods for them are existing at > the receiving side (I checked this by looking at and stepping through the > generated javascript code.) > In my small sample application I forced the GWT-compiler to generate > specific methods of a class by creating a dummy instance and calling its > methods in onModuleLoad(). As soon as those were generated to javascript I > could pass an object of the same type from another module and use its > methods. > If I didn't create these dummies and "dummy"-use their methods the > javascript code was not generated and it ended up calling > null.nullMethod(). I believe this is due to the pruning phase during > optimization steps of the compile process. > > Long story, short question: Can I disable this pruning step for selected > classes (or even methods) of my java classes? > Or is there another way to force the compiler to generate these methods to > javascript? > > With kind regards, > Erik > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/hNtg34rQf1sJ. > To post to this group, send email to google-web-toolkit@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com. > 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 google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
