Note: The component performing identity constraint collection and validation is responsible for providing an implementation of this interface. The component is also responsible for performing the necessary checks required by each type of identity constraint. @xerces.internal @author Andy Clark, IBM @version $Id: ValueStore.java,v 1.2.6.1 2005/09/08 08:58:34 sunithareddy Exp $
Note: The component performing identity constraint collection and validation is responsible for providing an implementation of this interface. The component is also responsible for performing the necessary checks required by each type of identity constraint. @xerces.internal @author Andy Clark, IBM @version $Id: ValueStore.java 520039 2007-03-19 18:34:38Z mrglavas $
Note: The component performing identity constraint collection and validation is responsible for providing an implementation of this interface. The component is also responsible for performing the necessary checks required by each type of identity constraint. @author Andy Clark, IBM @version $Id: ValueStore.java,v 1.4 2003/05/08 20:11:56 elena Exp $
Note: The component performing identity constraint collection and validation is responsible for providing an implementation of this interface. The component is also responsible for performing the necessary checks required by each type of identity constraint. @author Andy Clark, IBM @version $Id: ValueStore.java,v 1.4 2001/05/15 17:21:25 neilg Exp $
Purpose The ValueStore interface exposes the property model in SDO to pluggable implementers that wish to wrap their object model in the SDO API.
The ValueStore interface exposes the properties Map in SDODataObject to extension or replacement. The implementing class must override or extend the get/set/isSet/unset ValueStore functions so that any calls routed through the SDO API are routed through to the underlying Data-Model that ValueStore wraps.
Possible implementers must maintain DataObject integrity which includes containment and changeSummary.Setup:
Before using the ValueStore interface the type tree must be defined by loading in the XSD schema file that matches the plugged in model if using dynamic classes.
The ValueStore interface enables 3rd party implementers of the SDO API to plug-in their object model in place of the default SDO DataObject interface. The Map like functions set/get and the List like functions isSet/unset are left to the implementation to maintain.
It is the responsibility of the implementation to handle read or read/write capability against the underlying object model. Any access or modification of the pluggable object model done outside of this interface may destabilize the ValueStore state.
|
|
|
|
|
|
|
|
|
|