anchor.diff:  
   Based on those files, we can create a subclass of the design that uses a [classname]#BeanBinder# to automatically connect bean properties to field instances.
   This will look at all instance fields that are of a Field type in the class and try to find a bean property with the same name.
  -The binder will automatically use a [interfacename]#ConverterFactory# to find a converter in case the type of the field component doesn't match the type of the bean property.
   
   [source, java]
   ----
  
positive.code: 
  binder.forField(titleField)
    // Shorthand for requiring the field to be non-empty
    .setRequired("Every employee must have a title")
    .bind(Person::getTitle, Person::setTitle);
  ----
  
  
negative.code: Label nameStatus = new Label();
  
  binder.forField(nameField)
    // Define the validator
    .withValidator(
      name -> name.length() >= 3,
      "Full name must contain at least three characters")
    // Define how the validation status is displayed
    .withValidationStatusHandler(status -> {
        nameStatus.setValue(status.getMessage().orElse(""));
        nameStatus.setVisible(status.isError());
      })
    // Finalize the binding
    .bind(Person::getName, Person::setName);
  ----
  
  It is possible to add multiple validators for the same binding.
  The following example will first validate that the entered text looks like an email address, and only for seemingly valid email addresses it will continue checking that the email address is for the expected domain.
  
  [source, java]
  