|
|||||||||
| PREV NEXT | FRAMES NO FRAMES | ||||||||
AbstractSDKCall provides a base implementation of
SDKCall.Connection.
Connection to
a JDBC database.ContainerPolicy.DatabaseRow to an XML document.FieldTranslator
interface.XMLTranslator
interface.DatabaseRow from those defined in the data store to
those expected by the appropriate Descriptor(s)
and vice versa.ClassLoader abstract class.mark
and reset methods.
VARRAYs except internally they store their information in a separate table
from their parent structure's table.org.xml.sax.SAXParseException class.org.xml.sax.SAXParseException class,
providing indirect access to its protocol via an interface.SDKAccessor is a facile implementation
of the Accessor interface.SDKCall augments the Call interface
to define a bit more
behavior, as required by the SDKQueryMechanism:
When a query is executed, it is cloned; the call must be
able to provide a clone of itself that corresponds to this cloned query.SDKCollectionMappingHelper
to interact
with the assorted SDK collection mappings.SDKDescriptor supplements
the Descriptor protocol with a number of defaults and
helper methods that simplify the use of custom queries/calls
(since every query in an SDKDescriptor must be custom).SDKDirectCollectionMapping
consolidates the behavior of mappings that
map collections of "native" data objects (e.g.SDKFieldValue is a container for nested
(and possibly repeating) elements that might occur
within a database row.SDKLogin does little more than
parameterize Accessor to be used by the
Session.SDKObjectCollectionMapping
is used to represent
a relationship between a single
source object and collection of target objects; where,
on the data store, the source object has a collection of
references (foreign keys) to the target objects.SDKPlatform provides just a tiny bit of behavior:
building the queries for using sequence numbers.SDKQueryMechanism class implements the
DatabaseQueryMechanism protocol by redirecting
all queries to a collection
of calls that is provided to the mechanism when it is built.SchemaManager for SDK developers.java.sql.Connection.
FieldTranslator
interface.#toString(PrintWriter), to allow subclasses to
insert additional information.
#toString(PrintWriter), to allow subclasses to
insert additional information.
Accessor in the XML context.XMLStreamPolicy
interface
simply forwards any message to the accessor, which is assumed to be an
XMLAccessor.XMLCall does not do much.XMLDescriptor extends
the SDKDescriptor protocol with a number of defaults and
helper methods that simplify the use of XML data store.DocumentImpl class
to override the Text Node factory method.XMLFileAccessor is an implementation
of the XMLAccessor interface that uses the
native O/S file system to store XML documents:
The base directory is analogous to a relational database that
contains a collection of related tables.XMLFileLogin holds the information required to log in to a
file-based XML data store, using an XMLFileAccessor.XMLStreamPolicy interface
simply wraps the supplied file (or files) in the appropriate stream (or
enumeration of streams).XMLLogin adds a little protocol to make it
look like we are dealing with XML documents and elements instead of
database rows and fields.XMLPlatform implements various database platform behaviors in
a way that is useful for an XML data store:
Building the calls necessary for XML "sequence numbers".SchemaManager
to create XML stream sources and sequences for XML Projects.XMLStreamPolicy interface
simply returns the supplied stream (or streams).DatabaseRow.XMLFileAccessor
class;
supplanting subdirectories with ZIP files.XMLStreamPolicy
interface
provides streams to XML documents stored in ZIP file archives.
|
|||||||||
| PREV NEXT | FRAMES NO FRAMES | ||||||||