Skip navigation links

oracle.adf.model.binding
Interface DCBindingContainerValidationListener

All Superinterfaces:

java.util.EventListener

All Known Subinterfaces:

JUPanelValidationListener

All Known Implementing Classes:

DCBindingContainerValidationAdapter, JUPanelValidationAdapter

public interface DCBindingContainerValidationListener

extends java.util.EventListener

Implemented by classes that are interested in performing typically lightweight, client-side validation for an attribute, a row, or the whole transaction.

When the Event Inspector is used to generate PanelValidationEvent code on a PanelBinding object, it adds this interface to the list of interfaces the concerned class implements and also implements the three event methods.

Method Summary

void	beforeCurrencyChange(DCBindingContainerValidationEvent ev) Invoked before a JClient binding object calls a navigation event to display the next row data in the JClient controls.
void	beforeSaveTransaction(DCBindingContainerValidationEvent ev) Invoked before a JClient binding object calls commit() on the transaction to save any pending changes into the database.
void	beforeSetAttribute(DCBindingContainerValidationEvent ev) Invoked before a JClient Binding object calls Row.setAttribute() to update a value from a binding object into the corresponding Row object.

Method Detail

beforeSetAttribute

void beforeSetAttribute(DCBindingContainerValidationEvent ev)

Invoked before a JClient Binding object calls Row.setAttribute() to update a value from a binding object into the corresponding Row object.

Applications should perform lightweight, attribute-data validation (for example, matching a value with a small set of values or uppercasing all entries etc.) at this level before the value is passed on to BC4J. Note that such a validation should be duplicated on the BC4J side too as other clients or APIs may modify the same attribute. This duplication is usually necessary when a client needs immediate feedback of an error rather than going over to the middle-tier (in a multi-tier platform) and get any errors.

beforeCurrencyChange

void beforeCurrencyChange(DCBindingContainerValidationEvent ev)

Invoked before a JClient binding object calls a navigation event to display the next row data in the JClient controls.

Applications should perform lightweight, row-data validation (for example, inter-attribute validation etc.) at this level before the value is passed on to BC4J. Note that such a validation should be duplicated on the BC4J side to allow other clients or APIs to modify the same attribute. This duplication is usually necessary when a client needs immediate feedback of an error rather than going over to the middle-tier (in a multi-tier platform) and get any errors.

beforeSaveTransaction

void beforeSaveTransaction(DCBindingContainerValidationEvent ev)

Invoked before a JClient binding object calls commit() on the transaction to save any pending changes into the database.

Applications should perform lightweight, panel-level validation (for example, validating that all desired values are filled in etc.) at this level before the values are passed on to BC4J. Note that such a validation should be duplicated on the BC4J side to allow other clients or APIs to modify the same attribute. This duplication is usually necessary when a client needs immediate feedback of an error rather than going over to the middle-tier (in a multi-tier platform) and get any errors.

Skip navigation links