Overview | Module | Use | Devguide | Index

Services' Summary | Interfaces' Summary | Properties' Summary | Services' Details | Interfaces' Details | Properties' Details

:: com :: sun :: star :: configuration :: backend ::
service Schema
Description provides read only access to a configuration component schema. A component is a set of hierarchically organized and semantically related configuration settings, e.g StarWriter settings. A component schema contains two separate sections, one which describes the templates to be used in the dynamic containers (sets) of the component and one which describes the component's data structure. Since OOo 1.1.2 See also Layer Service providing access to individual configuration data for an entity.

Exported Interfaces - Summary
XSchema | handles access to the schema data for a component. (details)

Properties' Summary
[ readonly ] string URL | [ OPTIONAL ] The URL of the layer data.

Exported Interfaces - Details
XSchema
Description handles access to the schema data for a component. The data can be read either in its entirety (templates and component description) or each of its parts can be accessed.

Properties' Details
URL
[ readonly ] string URL; Usage Restrictions optional Description The URL of the layer data. Since OOo 2.0

Top of Page

Copyright © 2000, 2013 LibreOffice contributors and/or their affiliates. All rights reserved.

LibreOffice was created by The Document Foundation, based on OpenOffice.org, which is Copyright 2000, 2010 Oracle and/or its affiliates.

The Document Foundation acknowledges all community members, please find more info at our website.

Privacy Policy | Impressum (Legal Info) | Copyright information: The source code of LibreOffice is licensed under the GNU Lesser General Public License (LGPLv3). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.