MyEclipse for Spring

Code Reference: CustomerEditor.java

Skyway Builder 8.6MyEclipse for Spring 8.6Reference edition

The editor class owns the form state for the customer screen. This page describes its responsibilities and the events it handles.

Diagram of the model view controller pattern with a request moving from the browser to the controller, service and data layers — Figure 24. The editor holds form state and delegates persistence to the service.

CustomerEditor is the form state holder for the customer screen. It reads the record to edit, exposes the values to the view and collects the submitted values. It does not decide what to do with them. That decision belongs to the service that the editor calls on submit.

Responsibilities

Load the record for an edit request, or create an empty record for a new entry.
Expose the current values to the form view.
Accept submitted values and hand them to the service.
Report the outcome so that the view can show a message.

Events

The editor listens for a small set of events: save, cancel and remove. Each event calls one service method and then updates the editor state. Keeping the event list short makes the screen easy to test and easy to explain.

Keep the editor dumb. No validation rules and no database calls inside the editor. Those belong to the validator and the service, where they can be reused by other screens.

When a screen needs a second form, create a second editor rather than growing this one. One editor per screen keeps the state and the events small enough to review.

Responsibilities

Events

Reference shelf

Continue reading