Package com.epicentric.contentmanagement

Supports integrated access to content stored in multiple content management systems.

See:
Package Summary

Interface Summary

ContentItem	Specification of the behaviors for a folder or a document object in the content management system.
Document	Representation of a read-only document object in the content management system.
Folder	Object representation of a read-only container for Document and other Folder objects.
PropertyDefinition	Encapsulates information about a single property.
StringPropertyDefinition	Encapsulates additional information for String properties.
WorkflowStage	Object representation of the workflow stages obtained by a workflow-aware folder.
WorkflowTask	Object representation of the tasks within each WorkflowStage.
WritableContentItem	Write-related behavior specification for a folder or document object in the content management system.
WritableDocument	Write-related behavior specification for a writable document in the content management system.
WritableFolder	Write-related behavior specification for a writable folder in the content management system.

Class Summary

ContentManager	Entry point into the CAM API.
ContentUtils	Utility functions that can be used package-wide.
RunIndexer	Command line utility class for indexing selected folders.

Exception Summary

ContentAlreadyExistsException	Exception that is thrown when attempting to create a folder, document, or property that already exists and an override or append is not allowed.
ContentCommunicationException	Exception that is thrown when the communication with the content middleware or content connector is down.
ContentException	Exception class having the features of a regular exception in addition to allowing nested exceptions.
ContentFeatureNotSupportedException	Exception that is thrown when a feature (an interface) is not supported.
ContentInaccessibleSecurityException	Exception that is thrown when permissions are insufficient to see a folder, document, or property.
ContentLockedException	Thrown when attempting to acquire a lock on a document that is already locked.
ContentNotFoundException	Exception that is thrown either when a folder, document, or property cannot be found, or when a folder or document can't be accessed due to lack of permission.
ContentNotLockedException	Thrown when attempting to perform an action on an unlocked document that requires the document to be locked.
ContentSecurityException	Exception that is thrown when permissions are insufficient to act on a folder, document or property.
PropertyNotSupportedException	Indicates that the specified property is not supported.
PropertyTypeMismatchException	Indicates that the specified property type does not match the type in the property definition or is not a supported custom property type for this item.

Package com.epicentric.contentmanagement Description

Supports integrated access to content stored in multiple content management systems. This package is part of the Vignette Content Access Management (CAM) Suite, which enables plug-in of third-party content management systems. Vignette Portal ships with a group of PortalBeans that use CAM to provide content viewing, publishing, search, taxonomy, and lightweight content management and workflow.

Customers can use the interfaces and classes in this package to develop their own CAM PortalBeans or to interact with a content management system. The source of content can be transparent to users; for example, a (PortalBean) built on this package can integrate content from any number of sources.

CAM plugs in to back-end systems through software components known as connectors. Each data source -- file system, relational database, third-party content management system, etc. -- has its own connector. In addition, Vignette Portal search and indexing services are provided through connectors to search engines. The following diagram provides a high-level overview of the CAM and Vignette Portal searching and indexing architecture:

CAM has two public APIs: the Access API provided by this package and the Connector API provided by the com.epicentric.contentmanagement.connectors package. These APIs are capability-based; they query the underlying system about its capabilities and respond accordingly. For example, com.epicentric.contentmanagement.Folder in the Access API includes canCreateSubfolders() and getSubfolder(String name) methods that call through to connector-specific implementations of corresponding methods in com.epicentric.contentmanagement.connectors.ConnectorFolder of the Connector API.

The CAM middleware provides the actual implementation of the Access API and is not public. At this time, the Vignette Portal search and indexing API is also not public.

For additional documentation of the CAM APIs, see Vignette Portal Developer's Guide available from Vignette Global Marketplace, http://global.vignette.com.

See Also:

com.epicentric.contentmanagement.connectors, com.epicentric.portalbeans