*Index
*News
*Status
*Changelog
*Contributors
Downloads
*Releases
*Nightly
Resources
*Source
*Mailing Lists
*CVS
*Library
User's Guide
*Installation
*Configuration
*FAQ
*Examples
*Tomcat Howto
*Avalon Howto
Programmer's Corner
*Architecture
*Domain
*Namespace
Slide API
*Structure
*Security
*Lock
*Content
*Macro
*Index
*Process
WebDAV
*General Info
*Clients
API Reference
*JavaDoc
*WebDAV Client
     Installation
 Dependencies
Slide
WebDAV Servlet

Dependencies

Slide has dependencies to some external function libraries. Some of these dependencies are both compile-time and runtime dependencies, while some are only runtime dependencies. Some build options also require additional external libraries.

Slide depends on the following software libraries at build time :
*Jakarta Ant 1.2
*Sun JAXP 1.1
*Sun Servlet API 2.2

Slide depends on the following software libraries at run time :
*Sun JAXP 1.1
*A JAXP-compliant XML parser
*Sun Servlet API 2.2

Slide can be managed at run time if it is run on top of a management framework like Apache Avalon or Sun JMX.

As said above, the requirements for the various build options can vary. Some might require :
*Tomcat 4.0
*Apache Avalon
*A JMX MBean server, and the JMX libraries

Slide

If you want to build an application which uses the Slide API, just add the slide.jar to your classpath. Then, be sure to put the domain configuration file in the appropriate directory. By default, it is a file called "Domain.xml" placed in the directory from which the JVM is started.

WebDAV Servlet

The WebDAV servlet requires a servlet container which supports at least the 2.2 API. The easiest solution is to use the web application archive which is included in the slide distribution (webapp/slide.war) and deploy it in your servlet container. The WAR file contains a "Domain.xml" file which should be modified to configure the domain.


 
Java, JDBC, JNDI, Sun, Sun Microsystems are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and in other countries. All other product names mentioned herein are trademarks of their respective owners.
 

The Apache Software Foundation. (C) 2000. All rights reserved