I can report that at least as of 2.8.1, you get an exception if you specify
an that doesn't implement EntryPoint, but still has the
correct public void onModuleLoad() signature. I didn't investigate too
deeply, but the compiled output was something like null.onModuleLoad(),
which indicated to
Do you mean that the class (or superclass) had a public void onModuleLoad()
method but no implements EntryPoint?
I know that the mere presence of an onModuleLoad method (even a static one)
was enough to turn any class into an entry point, and it's possible that it
changed at some point; but
> I figured it out. The entry point class extended another class that
> implemented EntryPoint, but did not explicitly say that it implemented
> EntryPoint. This works fine in 2.6 but not in 2.8.
>
Sounds like a bug to me. Java inheritance should also apply for entry
points. Can you make a
I figured it out. The entry point class extended another class that
implemented EntryPoint, but did not explicitly say that it implemented
EntryPoint. This works fine in 2.6 but not in 2.8.
On Sunday, October 1, 2017 at 9:16:55 PM UTC-7, John Malpas wrote:
>
> I have a fairy complex web
I have a fairy complex web application (What Grows Here) with maps etc that
has been out for few years.
I have been compiling it in GWT 2.6. It compiles and runs just fine in 2.6.
This week I have been trying to move a bunch of GWT apps to 2.8.
This one application compiles quietly in 2.8, but
