Examples of UpdateValueStrategy

• org.eclipse.core.databinding.UpdateValueStrategy
  Customizes a {@link Binding} between two {@link IObservableValue observablevalues}. The following behaviors can be customized via the strategy:

  • Validation
  • Conversion
  • Automatic processing

  The update phases are:

  1. Validate after get - {@link #validateAfterGet(Object)}
  2. Conversion - {@link #convert(Object)}
  3. Validate after conversion - {@link #validateAfterConvert(Object)}
  4. Validate before set - {@link #validateBeforeSet(Object)}
  5. Value set - {@link #doSet(IObservableValue,Object)}

  Validation:
  {@link IValidator Validators} validate the value at multiple phases in theupdate process. Statuses returned from validators are aggregated into a MultiStatus until a status of ERROR or CANCEL is encountered. Either of these statuses will abort the update process. These statuses are available as the {@link Binding#getValidationStatus() binding validation status}.

  Conversion:
  A {@link IConverter converter} will convert the value from the type of thesource observable into the type of the destination. The strategy has the ability to default converters for common scenarios.

  Automatic processing:
  The processing to perform when the source observable changes. This behavior is configured via policies provided on construction of the strategy (e.g. {@link #POLICY_NEVER}, {@link #POLICY_CONVERT}, {@link #POLICY_ON_REQUEST}, {@link #POLICY_UPDATE}).

  @see DataBindingContext#bindValue(IObservableValue,IObservableValue,UpdateValueStrategy,UpdateValueStrategy) @see Binding#getValidationStatus() @see IValidator @see IConverter @since 1.0

Examples of org.eclipse.core.databinding.UpdateValueStrategy