[gwt-contrib] Class literals for JsTypes in superdevmode

2015-06-08 Thread Chris DiGiano
I'm having trouble referencing a JsType interface when running under superdevmode. I'm trying to pass the JsType as a class reference to a method that uses the class to coerce the results into the expected type: myelement.getCustomStampedElement(dialog, PolymerDialog.class).open();

Re: [gwt-contrib] Class literals for JsTypes in superdevmode

2015-06-08 Thread 'Ray Cromwell' via GWT Contributors
Ooops, wrong pointer (for external users) This one https://gwt-review.googlesource.com/#/c/12311/ On Mon, Jun 8, 2015 at 3:14 PM, Ray Cromwell cromwell...@google.com wrote: Try rolling back this CL and see if it fixes it (

Re: [gwt-contrib] Class literals for JsTypes in superdevmode

2015-06-08 Thread 'Ray Cromwell' via GWT Contributors
Try rolling back this CL and see if it fixes it ( https://critique.corp.google.com/#review/92873682/depot/google3/third_party/java_src/gwt/svn/trunk/dev/core/src/com/google/gwt/dev/jjs/impl/GenerateJavaScriptAST.java ) On Mon, Jun 8, 2015 at 3:04 PM, Chris DiGiano d...@google.com wrote: I'm

Re: [gwt-contrib] Class literals for JsTypes in superdevmode

2015-06-08 Thread 'Roberto Lublinerman' via GWT Contributors
This might be due to the way we handle class literals. Class literals for interfaces if not referenced during the initial compile might cause that error. The error should go aways if you restart SDM. The offending sequence is 0) Suppose initially you have (interface A, class B and class C) and