The Author Online Book Forums are Moving

The Author Online Book Forums will soon redirect to Manning's liveBook and liveVideo. All book forum content will migrate to liveBook's discussion forum and all video forum content will migrate to liveVideo. Log in to liveBook or liveVideo with your Manning credentials to join the discussion!

Thank you for your engagement in the AoF over the years! We look forward to offering you a more enhanced forum experience.

BobMarcum (10) [Avatar] Offline
#1
I would just like to confirm this. I assume this to be true.

If it is then why would you ever require specifying "super();" in a constructor... as in DashboardPanel? In every case where a class inherits another class (including where no explicit inheritence is specified in the code), by standard java rules, the parent is constructed before the child class, beginning with the top level class - Object - in the inheritence chain. In this process of construction the parent will be constructed using the default constructor ("super():") automatically, if no other constructor is specified.

I just want to confirm, because the text of the book makes a case - provides a reason - for specifying the default constructor in DashboardPanel.

Thanks.
robert.hanson (173) [Avatar] Offline
#2
Re: GWT complies with all of Java's compile and runtime rules ... correct?
> I just want to confirm

Confirmed. GWT makes every effort to follow the same exact semantics of Java. There are very few exceptions to this rule, the Serializable interface is one of them, where it is simply a synonym for IsSerializable.