ZK Developer's Reference/Data Binding/Validation

Validate Each Bean at onBindingSave

In additions to InputElement.setConstraint(String), Data Binding Manager provides an alternative way to do the validation.

Before saving a value into a bean, the onBindingSave event is sent to each of binding components, so that you could do the validation with your customized way by registering onBindingSave event listener in these components. For example,

<intbox value="@{person.age, save-when='btn.onClick'}">
<attribute name="onBindingSave">
   if (event.value < 18)
      throw new WrongValueException("Age below 18 is not allowed to enter this site.")
</attribute>
</intbox>

As shown above, the onBindingSave event is sent with an instance of BindingSaveEvent, and you could retrieve the detailed information from it.

Validate All Beans at onBindingValidate

After sending the onBindingSave events to all of binding components to make sure their values are validated, the Data Binding Manager will send an onBindingValidate event to the component which triggers data binding to work, for example, a button. For example,

<button id="btn" label="submit">
  <attribute name="onBindingValidate">
     if (myValidator.validate(event.getReferences(), event.getValues()))
         self.setAttribute("passed",true);
   </attribute>
  <attribute name="onClick">
     if (self.getAttribute("passed") == true)
         Executions.sendRedirect("index.zul");
  </attribute>
</button>

The onBindingValidate event is sent with an instance of BindingValidateEvent, and you could retrieve the detailed information from it. For example, the values could be retrieved by use of BindingValidateEvent.getValues(). A typical use is to start JSR 303 validation.

Finally, after posting all events of validation phase to all related ZK components, data binding will truly save data into data bean.

Version History

Version	Date	Content