(incubating) | The Free and Open Productivity Suite
Announcing Apache OpenOffice 3.4

Developer's Guide

API

SDK

Tips 'n' Tricks

Miscellaneous

Content for OpenOffice.org version 3.3.

:: com :: sun :: star :: configuration :: backend ::

service Backend
Description
provides access to a configuration database composed of one or more storage backends containing settings used by software modules.

Configuration data is organized into layers which are selected by components and entities.

Components are characterized by configuration schemas. A component contains configuration data for a particular application domain or software module.

Entities are organised hierarchically in organisations, groups, roles and individual users. Each element of the associated hierarchy corresponds to a layer that applies to an entity.

A layer contains data for multiple components associated to a single entity.

Since
OOo 1.1.2
Developers Guide
Config - Adding a Backend Data Store

Exported Interfaces - Summary
XSchemaSupplier

provides access to configuration schemas.

XBackend

provides access to the layer data.

XBackendEntities

provides information about supported and special entities. (details)

Exported Interfaces - Details
XSchemaSupplier
Description
provides access to configuration schemas.
XBackend
Description
provides access to the layer data.
XBackendEntities
Usage Restrictions
optional
Description
provides information about supported and special entities.

 
Top of Page

Apache Feather

Copyright & License | Privacy | Contact Us

Apache and the Apache feather logos are trademarks of The Apache Software Foundation. OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation. Other names appearing on the site may be trademarks of their respective owners.

Apache OpenOffice is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.