@JsExport exports constructors and static members and pins them so they act as entry points and not get pruned. On the other hand, @JsType enforces generation of javascript compatible prototype for the class so if there is a method named "someMethod" in the Java object, same method with same name exists in javascript object. So if you are coming from GWT-Exporter, you can have the same behavior by adding both JsExport and JsType to the same class that you want to use in javascript land (this part may change before we release the first phase of JsInterop - it is little bit confusing)
On Sun, Feb 1, 2015 at 3:01 PM, Joseph Gardi <jgleo...@gmail.com> wrote: > I have a few questions about exporting: > It said: "@JsExport can only be applied to constructors, static fields > and static methods, and whole concrete classes. > ". Does this mean that we'll just continue to use GWT-exporter for this > or will there be another way. Also, what will be the easiest way to export > the API's of entire libraries? I had this need but decided it was too > difficult so I just used a javaScript library instead. > > On Monday, September 9, 2013 at 7:13:43 PM UTC-4, Goktug Gokdogan wrote: >> >> Interesting idea; though we still need an annotation when the name is not >> a valid java identifier and also can't find a good name to mark the >> exception case. >> Another issue is anyone who is not aware of convention can be surprised >> by it (e.g. developer renames a method and the method is no longer a js >> function). >> >> Do you aware of any popular java lib that solves a similar problem by >> conventions so that I can take a look for ideas? >> >> >> On Mon, Sep 9, 2013 at 12:18 PM, Jörg Hohwiller <joerg.h...@googlemail. >> com> wrote: >> >>> Hi Goktug, >>> >>> nice approach. IMHO getters and setters should not be required to be >>> annotated by @JsProperty. Instead a method looking like a getter or >>> setter that is actually not a property accessor should be annotated >>> (Convention over configuration). >>> I would love to see this coming... >>> >>> Cheers >>> Jörg >>> >>> -- >>> http://groups.google.com/group/Google-Web-Toolkit-Contributors >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "GWT Contributors" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com >>> . >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "GWT Contributors" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-web-toolkit-contributors/e19b5c6d-cbe0-4993-962b-ca01c3eb6d7a%40googlegroups.com > <https://groups.google.com/d/msgid/google-web-toolkit-contributors/e19b5c6d-cbe0-4993-962b-ca01c3eb6d7a%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA1fWZQQevrPEx1dXkpCJNLJXMAKn7-0ouDJdA2SG1zHNA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
