Skip navigation links

Package oracle.rules.sdk.store

Provides the interfaces and classes that allow for support of different repositories in the Oracle Business Rules SDK.

See:
Description

Interface Summary

DocumentID	A DocumentID identifies rule document(s) in a repository store accessed with a RepositoryConnection.
RepositoryConnection	The repository connection interface for the Oracle Business Rules Rules SDK.

Class Summary

AbstractRepositoryConnection	Provides a partial implementation of the RepositoryConnection interface.
Registration	This class is used to register an implementation of the RepositoryConnection with the RepositoryConnectionFactory.
RepositoryConnectionFactory	Factory for creating implementation instances of the Oracle Business Rules RepositoryConnection interface.

Exception Summary

DocumentException	Thrown when an error is encountered processing the document itself.
DocumentExistsException	Thrown by createDocument to indicate that a document corresponding the DocumentID already exists in the repository.
DocumentIDException	Thrown to indicate that the ID defined in an DocumentID object is not valid.
DocumentNotFoundException	Thrown to indicate that the DocumentID did not identify a document in the repository.
RegistrationException	Thrown when an error an attempt to register a RepositoryConnection fails.
StoreException	Thrown when an error is encountered with the underlying repository.

Package oracle.rules.sdk.store Description

Provides the interfaces and classes that allow for support of different repositories in the Oracle Business Rules SDK.

Package Specification

Overview

The Rules SDK uses the interfaces in this package to store and retrieve documents from an underlying repository. The RepositoryConnection interface represents the functionality required by the Rules SDK. The AbstractRepositoryConnection class provides a default implementation of RepositoryConnection. AbstractRepositoryConnection must be extended to enable a repository to be used by the Rules SDK.

If the underlying repository supports tags (sometimes called labels), then the class that extends AbstractRepositoryConnection should, in the init method, indicate that tags are supported by invoking the supportsOption method with the tags option.

Administrative operations are not exposed and must be performed externally. Administrative operations include repository configuration and, for source control systems, the creation and population of local views of repository content.

An implementation of RepositoryConnection must be registered with the RepositoryConnectionFactory prior to use (also see Registration). The key used to register and lookup the implementation should be documented. Implementations supplied by Oracle are automatically registered. Non-Oracle implementations should implement the following.

• The implementation class (or one of the classes) should include a static initialization block that registers the RepositoryConnection implementation with the RepositoryConnectionFactory.
• In a location that accessible via the CLASSPATH (normally the jar file containing the implementation), A properties file, oracle/rules/sdk/store/repository_connection.properties should be created. This properties file should contain the property, oracle.rules.sdk.store.plugin_classname. The value of this property should be the fully qualified class name of the class that implements RepositoryConnection.

During static initialization, the RepositoryConnectionFactory uses the getResources ClassLoader method to find all the instances of the repository_connection.properties file in the CLASSPATH. Then, it loads the class named in the oracle.rules.sdk.store.plugin_classname property from each properties file. During the loading of the class, the static initializer is executed which will register the implementation.

Skip navigation links