Return-Path: Delivered-To: apmail-incubator-jackrabbit-commits-archive@www.apache.org Received: (qmail 19436 invoked from network); 6 Dec 2005 10:07:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Dec 2005 10:07:30 -0000 Received: (qmail 11715 invoked by uid 500); 6 Dec 2005 10:07:29 -0000 Mailing-List: contact jackrabbit-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jackrabbit-dev@incubator.apache.org Delivered-To: mailing list jackrabbit-commits@incubator.apache.org Received: (qmail 11704 invoked by uid 500); 6 Dec 2005 10:07:29 -0000 Delivered-To: apmail-incubator-jackrabbit-cvs@incubator.apache.org Received: (qmail 11701 invoked by uid 99); 6 Dec 2005 10:07:29 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Dec 2005 02:07:29 -0800 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 06 Dec 2005 02:07:28 -0800 Received: (qmail 18996 invoked by uid 65534); 6 Dec 2005 10:07:08 -0000 Message-ID: <20051206100708.18995.qmail@minotaur.apache.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r354392 - /incubator/jackrabbit/trunk/jackrabbit/src/site/fml/faq.fml Date: Tue, 06 Dec 2005 10:07:08 -0000 To: jackrabbit-cvs@incubator.apache.org From: jukka@apache.org X-Mailer: svnmailer-1.0.5 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Author: jukka Date: Tue Dec 6 02:07:02 2005 New Revision: 354392 URL: http://svn.apache.org/viewcvs?rev=354392&view=rev Log: Various FAQ improvements. Modified: incubator/jackrabbit/trunk/jackrabbit/src/site/fml/faq.fml Modified: incubator/jackrabbit/trunk/jackrabbit/src/site/fml/faq.fml URL: http://svn.apache.org/viewcvs/incubator/jackrabbit/trunk/jackrabbit/src/site/fml/faq.fml?rev=354392&r1=354391&r2=354392&view=diff ============================================================================== --- incubator/jackrabbit/trunk/jackrabbit/src/site/fml/faq.fml (original) +++ incubator/jackrabbit/trunk/jackrabbit/src/site/fml/faq.fml Tue Dec 6 02:07:02 2005 @@ -28,8 +28,8 @@

JCR is the acronym of the JSR 170: Content - Repository for Java™ technology API. The JCR API is - a standardized interface for accessing a content repository. + Repository for Java™ technology API, a standard interface + for accessing content repositories.

@@ -62,8 +62,8 @@

- The Apache Jackrabbit is a fully featured content repository - implementation of the JCR API. The Jackrabbit project was started + The Apache Jackrabbit is a fully featured content repository that + implements all of the JCR API. The Jackrabbit project was started when the Day Software, the JSR-170 specification lead, licensed their initial implementation of the JCR reference implementation. Since then the Jackrabbit codebase @@ -84,6 +84,17 @@ Building Jackrabbit + + + How do I build the Jackrabbit sources? + + + See the Building Jackrabbit section + of the Jackrabbit documentation for + detailed build instructions. + + + Why does the Maven build fail with the message @@ -121,8 +132,24 @@ the Xalan-Java binary distribution and place them in the $MAVEN_HOME/lib/endorsed directory. Maven 1.1 users need to place the files in - $JRE/lib/endorsed as Maven 1.1 does not have a private - endorsed library directory. + $AVA_HOME/jre/lib/endorsed as Maven 1.1 does not have + a private endorsed library directory. +

+
+ + + + + Why does the Maven build fail with the message + "java.net.ConnectException: Connection timed out: connect"? + + +

+ This error message can appears when one of the Maven repositories + used for downloading Jackrabbit dependencies is not available. + This can happen if your network connection is broken or if the + repository server is down. Please check your network connection + or wait a while for the repository to come back online.

@@ -147,7 +174,7 @@ For Jackrabbit features (like access control and node type management) not covered by the JCR API, see the Examples page - on the wiki, the Jackrabbit javadocs (to be published on the web), + on the wiki, the Jackrabbit javadocs, or contact the Jackrabbit mailing list.

@@ -180,9 +207,39 @@

The JCR API does not contain features for creating or managing workspaces, so you need to use Jackrabbit-specific functionality - for creating new workspaces. See the related - mailing list thread - for more instructions. + for creating new workspaces. +

+

+ You can create a new workspace either manually or programmatically. + The manual way is to create a new workspace directory within + the repository home directory and to place a new + workspace.xml configuration file in that folder. + You can use the configuration file of an existing workspace as + an example, just remember to change the name of the workspace + in the <Workspace name="...">" tag. + See the Configuring Jackrabbit + page for configuration details. Note also that you need to restart + the repository instance to access the new workspace. +

+

+ The programmatic way is to acquire a Workspace instance + using the normal JCR API and to cast the instance to the Jackrabbit + WorkspaceImpl class. You can then use the + WorkspaceImpl.createWorkspace(String) + method to create new workspaces. +

+ + + + + + How do I delete a workspace in Jackrabbit? + + +

+ There is currently no programmatic way to delete workspaces. + You can delete a workspace by manually removing the workspace + directory when the repository instance is not running.