Ok that makes sense - but only for the @JsType(isNative = false) case. For the isNative = true JS already knows how to call JS. Correct?
Right now jsniterop gives an error in both cases. On Thu, Aug 18, 2016 at 6:30 PM, Jens <[email protected]> wrote: > I think simply calling from Java into JS using @JsType(isNative = true) as > in your example is not an issue. GWT would simply assume that the JS > function $ can handle the parameter. > > However when JS calls into a Java object that implements a @JsType, its > not clear which method implementation to choose without additional dispatch > logic. > > -- J. > > -- > You received this message because you are subscribed to the Google Groups > "GWT Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- Vassilis Virvilis -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
