Web Service Data Types

Document created by resplin Employee on Jun 6, 2015Last modified by alfresco-archivist on Aug 31, 2016
Version 6Show Document
  • View in full screen mode

Obsolete Pages{{Obsolete}}

The official documentation is at: http://docs.alfresco.com



Web Services
Back to Alfresco Content Management Web Services.





Introduction


Alfresco's Web Services use the following data types within input and output messages.

The definitive XML schema representation can be found here.


Change Log


Web Service Data Types Version 1.3


Identifiers & Locators


Store


The store data type uniquely identifies a store in a repository.

It is made up of two parts:


  • xsd:string scheme:  this indicates the type of store being referenced ths most common being 'workspace'.  Other valid store schemes include 'versionStore', 'user', 'search' and 'system'.
  • xsd:string address: this is the name of the store.

The most common example is the store used by the main web UI this has scheme 'workspace' and address 'SpacesStore'.


Reference


A reference data type is a reference to a single node within a given store.

A reference is made up of three parts:


  • xsd:string store: the details of the store that this reference is scoped by.
  • xsd:string uuid: the unique identifier of a node.  This part is optional.
  • xsd:string path: the query path to a single node.  This part is optional.

A reference which has only the store set is referring to the root node of that store.

A reference which has the uuid set (any may also have the path set) is referring to the node that has that uuid.  If no match is found then that is considered an error.

A reference which has only the path set is referring to a node that results from the execution of the given query on the store.  The query language expected is XPath.  For example to find the company home node in the 'SpacesStore' you would use the path /app:company_home.  If the result from the path query is more than one node then this is considered an error.


ParentReference


A parent reference is used to describe how a node may be associated to a child.  Parent references are usually used when an operation creates a new node, for example create content, move, etc.

A parent reference is made up of three parts:


Content Representation


ContentFormat


The content format data type is made up of two parts:


  • xsd:string mimetype:  the mime type of the content
  • xsd:string encoding: the character encoding of the content

This is used to encapsulate the content format information about a content node.


NamedValue


The named value data type contains the name and value(s) of an attribtue of the Alfresco repository:


  • xsd:string name: the string representation of values QName
  • xsd:boolean isMultiValue: indicates whether we are dealing with a multi-values attribute.  If set to false then the values attribute is used, otherwise the values attribute is used.  If this attribute is not set then it is interpreted as false.
  • xsd:string value: the single value as a string
  • xsd:string[] values: a string array of values 

The named value data type is most commonly used to prepresent the name and value of a node property.


Node


The Node data type represents the details of a node held within the repository.  It includes the type, aspect and property details and values.

The Node data type is made up of four parts:


  • Reference reference: the reference to the node
  • xsd:String type: the string representation of the QName of the type of the node
  • xsd:String aspect: the string representation of the QName's of the aspect applied to the node
  • NamedValue[] properties: the names and values of the properties of this node

Queries


Query


The query data type is made up of two parts:


  • xsd:string language: the query language, for eample Lucene or XPath.
  • xsd:String statement: the query statement

The query data type is used to encapsulate information about a query.


ResultSet


datatype_queryresult.jpg


Predicate


datatype_predicate.jpg


Meta Data


ClassDefinition


datatype_classdefinition.jpg


NodeDefinition


datatype_nodedefinition.jpg


Versioning


VersionHistory


datatype_versionhistory.jpg

Outcomes