4.9. Specifying bindings explicitly
Prev | 4. Rendering views | Next

## 4.9. Specifying bindings explicitly

Use the `binder` element to configure the exact set of model bindings usable by the view. This is particularly useful in a Spring MVC environment for restricting the set of "allowed fields" per view.

    <view-state id="enterBookingDetails" model="booking">
        <binder>
            <binding property="creditCard" />
            <binding property="creditCardName" />
            <binding property="creditCardExpiryMonth" />
            <binding property="creditCardExpiryYear" />
        </binder>
        <transition on="proceed" to="reviewBooking" />
        <transition on="cancel" to="cancel" bind="false" />
    </view-state>

If the binder element is not specified, all public properties of the model are eligible for binding by the view. With the binder element specified, only the explicitly configured bindings are allowed.

Each binding may also apply a converter to format the model property value for display in a custom manner. If no converter is specified, the default converter for the model property's type will be used.

    <view-state id="enterBookingDetails" model="booking">
        <binder>
            <binding property="checkinDate" converter="shortDate" />
            <binding property="checkoutDate" converter="shortDate" />
            <binding property="creditCard" />
            <binding property="creditCardName" />
            <binding property="creditCardExpiryMonth" />
            <binding property="creditCardExpiryYear" />
        </binder>
        <transition on="proceed" to="reviewBooking" />
        <transition on="cancel" to="cancel" bind="false" />
    </view-state>

In the example above, the `shortDate` converter is bound to the `checkinDate` and `checkoutDate` properties. Custom converters may be registered with the application's ConversionService.

Each binding may also apply a required check that will generate a validation error if the user provided value is null on form postback:

    <view-state id="enterBookingDetails" model="booking">
        <binder>
            <binding property="checkinDate" converter="shortDate" required="true" />
            <binding property="checkoutDate" converter="shortDate" required="true" />
            <binding property="creditCard" required="true" />
            <binding property="creditCardName" required="true" />
            <binding property="creditCardExpiryMonth" required="true" />
            <binding property="creditCardExpiryYear" required="true" />
        </binder>
        <transition on="proceed" to="reviewBooking">
        <transition on="cancel" to="bookingCancelled" bind="false" />
    </view-state>

In the example above, all of the bindings are required. If one or more blank input values are bound, validation errors will be generated and the view will re-render with those errors.

Prev | Up | Next
4.8. Suppressing binding | Home | 4.10. Validating a model