9.3. Editor types

We mentioned earlier that editors are Java objects conforming to the editor contract. In order for a Java object to be an editor, it has to implement either the Editor interface or one of the Editor subinterfaces. We emphasized earlier that the purpose of editors is to reduce the amount of code required for moving data from a domain object to the UI and back to the domain object. Most editors are therefore widgets, but they don’t have to be. You’re free to define “headless” editors, that is, without any UI, changing the state of properties where editing of a domain object is programmatically done.

Besides implementing one of the editor types, an editor has to specify zero or more fields in its body. These fields have a correlation ...

Get GWT in Action, Second Edition now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.