Overloading methods and GWT-Exporter

[David La Motta]

Hi.

How does the GWT-Exporter deal with method overloading?  I've taken the approach of creating a new project, which extends the original GWT project, that will ultimately be exported using GWT-Exporter--following one of the suggestions in the documentation.

I am hitting, unfortunately, problems with methods that are overloaded, getting error messages such as:

[ERROR] Ambiguous method signature lienzo.client.core.Context2D::drawImage(Lcom/google/gwt/dom/client/Element;DDDDDDDD) would conflict in JS with another method

How exactly should I deal with overloaded methods?  Clearly, GWT is getting around this somehow (surely it is renaming things as it translates to JS), but when exporting situations like this cause problems.

Thanks in advance.

// David

[Manuel Carrasco Moñino]

yes, gwtexporter supports method overload. There could be edge cases wich could fail. Attach some simple code which fails so as we can see if its a bug.

- manolo

--
 
 

[David La Motta]

Hi Manolo, 

We have overloaded methods such as:

public Context2D drawImage(ImageJSO image, double sx, double sy, double sw, double sh, double x, double y, double w, double h)

and

public Context2D drawImage(Element image, double sx, double sy, double sw, double sh, double x, double y, double w, double h)

Where ImageJSO is a [public inner] class of ours that extends from JavaScriptObject, and Element is a GWT class, which also extends from JavaScriptObject.

Could that be causing trouble?

Thanks for the help.

// David

[Manuel Carrasco Moñino]

Thats the problem, you can not overload a method with the same number of arguments and same types in exporter. In js JavaScriptobjects have the same signature, since they are gwt overlay types which can be cast.

- Manolo

--
 
 

[David La Motta]

Thanks, Manolo.  @NoExport on some of the overloaded methods clears the ambiguity problem.

// David

--