XWiki Data Model

Last modified by Manuel Smeria on 2013/02/20 07:47

XWiki is not just your average wiki engine; it exposes a flexible data model that can be leveraged at the presentation level. Combined with its powerful presentation level scripting capabilities, XWiki's data model can help you build simple to complex Web applications with little or no need to access the XWiki core. In other words, you can build custom applications through the XWiki web interface without having to compile, package, and deploy software components.

This area explains XWiki's data model of Classes, Properties, and Objects for those users who want to build applications primarily at the presentation level. It will help you understand how you can achieve significant features by programming at this level alone.

For information about XWiki's underlying database schema (tables and fields), see: XWiki's Database Schema.

XWiki Classes, Objects, and Properties

If you are familiar with object oriented programming, you understand the concept of classes, properties, and objects. The presentation level data model that XWiki exposes is much the same.

Classes
An XWiki class is like a template that defines a unique type of object. It defines what properties an object can have. When you define a custom class, you are saying that your application may need to create one or many objects (instances) of that class. The class itself is like a cookie cutter and the objects are unique instances of that class. So, in this analogy, if the class is the cookie cutter, the objects are the cookies (and we are talking about real edible cookies in this analogy; not Web cookies).
A class is attached to a page. There can be at most one class per page. The class name is the name of the document it is attached to.
Properties
Properties are the characteristics that an object can have. In a class definition, the properties define the data fields that each unique instance of the class can have values for. Properties have displayers which control how the property value is displayed in view or edit mode. Some displayers use advanced pickers to help you input a valid property value.
XWiki currently supports the following kinds of properties (data types):
  • Number
  • String
  • TextArea
  • Password
  • EMail (new in 4.2M3)
  • Boolean
  • Static List
  • Database List
  • Database Tree List
  • Document List (new in 4.2M3)
  • Date
    datePicker.png
  • User List
    userPicker-editSingle-objectEditor.png userPicker-editMultiple.png userPicker-viewMultiple.png
  • Group List
    groupPicker-editMultiple.png
  • Computed pseudofield (new in 4.2M3)
Starting with version 4.3M2 you can define your own property types.
Objects
Objects are unique instances of a class with unique values defined for each of the properties that make up the class.
An object is attached to a specific page. Each page can have multiple objects.
Using objects, you insert structured information in the wiki, while in a traditional wiki you can only enter unstructured information (plain text). This is one of the reasons why XWiki is a second generation wiki.

In summary:

  • Classes define an object type and the properties that are possible for an object of that type to have.
  • Properties define the types of data that unique objects can have. The property types (datatypes) are defined for the class, but the actual values for the properties are defined for the objects when the objects are instantiated from the class.
  • Objects are unique instances of a class with unique values for all of the properties that the class definition allows the objects to have.
Tags:
Created by VincentMassol on 2006/12/05 14:22

Get Connected