The Jakarta Project The Jakarta Slide Project

Main

Resources

User's Guide

Administrator's Guide

HOW-TOs

Programmer's Corner

Slide API

Reference

Introduction

Slide's architecture is a matrix of modules, from high-level services to low-level services and clearly separates functionality around different aspects (structure, security, locking and versioning).

The high-level interfaces are meant to provide a simple, standardized way of manipulating a namespace. Underneath these clean interfaces lie "pluggable" service implementations, which are the low-level services.

There exist tight dependencies between the high-level services because of the need to enforce security, locking and other contraints throughout the offered client API.

External Architecture

Internal Architecture

Transaction Management

The Slide API
Content management

The content management system is accessible through a set of Java classes, called helpers, which encompass all the functionality a client application will want to access.

The following helpers are provided :

  • structure : Access to the namespace tree
  • security : Security functions
  • lock : Locking functionality
  • content : Manage object revisions, metadata and content
  • macro : Higher level object management functions
  • index : Indexing and searching functions (not implemented yet)
  • process : Handles approvals, confirmations, notifications (not implemented yet)

More details on the helpers can be found on the appropriate section of the documentation. The domain page also contains details on how to access the helpers.

WebDAV

A client can access Slide remotely through WebDAV. A low-level client library is provided within the Slide project, as well as administration tools. This interface will expand over time to provide expose virtually all the functionality of the content management API.


Copyright © 1999-2001, Apache Software Foundation