com.bea.content

com.bea.content  Package

This package and sub-packages work together to provide BEA Portal Content Management. BEA Portal Content Management centers around the Virtual Content Repository. The Virtual Content Repository performs two functions:

  1. First, it acts as a content federator to SPI implementations by forwarding content actions to the appropriate configured Repository.
  2. Second, it optionally adds Library Services to configured BEA Repositories. Library Services adds WorkSpace, Versioning and a Simple LifeCycle to type defined properties (non-system properties) in a BEA Repository. The basic flow for a Node in a Library Services Enabled Repository is as follows:

This package and sub-packages work together to provide BEA Portal Content Management. It includes:

The components that make up a Virtual Repository are listed below.

Class Summary

BinaryValue

This class represents binary content.

ContentContext

ContentEJBHomeCache

This class caches the initial context and the EJB Home so lookups for EJBs are faster.

ContentEntity

A ContentEntity is an object that is identified in the content management system by a unique id.

Credentials

The credentials for an authenticated subject.

ID

The ID of a content element.

Node

A Node represents an element in a hieararchy.

ObjectClass

ObjectClass is the type for a Node.

PathHelper

Utility class to manipulate unix path like Strings such as /a/b/c/d.

Property

Property is a name value pair, with the name being unique relative to the Node and the value is an Array of Value objects.

PropertyChoice

PropertyChoice defines a set of choices for a PropertyDefinition, and thus any Property instances based on it.

PropertyDefinition

PropertyDefinition defines the shape of a Property.

Value

The value for a Property.

Exception Summary

AuthenticationException

This Exception is thrown when a user fails authentication.

AuthorizationException

Thrown if a user is not authorized for an action.

NodeExistsException

Thrown if an operation on a Node that already exists occurs, such as attempting to rename a Node to the Name of a Node that already exists.

NoSuchNodeException

Thrown if an operation on a Node that does not exist occurs.

NoSuchObjectClassException

Thrown if an operation on a ObjectClass that does not exist occurs.

NoSuchPropertyChoiceException

Thrown if an operation on a PropertyChoice that does not exist occurs.

NoSuchPropertyDefinitionException

Thrown if an operation on a PropertyDefinition that does not exist occurs.

NoSuchPropertyException

Thrown if an operation on a Property that does not exist occurs.

ObjectClassExistsException

Thrown if trying to create an ObjectClass that already exists.

PropertyChoiceExistsException

Thrown if trying to add a PropertyChoice to an ObjectClass with the same name as one that already exists.

PropertyDefinitionExistsException

Thrown if trying to add a PropertyDefinition to an ObjectClass with the same name as one that already exists.

PropertyExistsException

Thrown if trying to add a Property to a Node that already has a Property with the same name.

RepositoryException

This is the main checked exception for any error thrown from the SPI.

RepositoryRuntimeException

This is the main runtime exception for system errors.

UnsupportedRepositoryOperationException

An exception thrown from a repository implementation to signify that the operation is not supported by the implementation.