Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 30682 invoked from network); 22 Aug 2007 11:16:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Aug 2007 11:16:38 -0000 Received: (qmail 22668 invoked by uid 500); 22 Aug 2007 11:16:34 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 22647 invoked by uid 500); 22 Aug 2007 11:16:34 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 22638 invoked by uid 99); 22 Aug 2007 11:16:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Aug 2007 04:16:34 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Aug 2007 11:16:32 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1INoC3-0000yo-DW for users@jackrabbit.apache.org; Wed, 22 Aug 2007 04:16:11 -0700 Message-ID: <12272534.post@talk.nabble.com> Date: Wed, 22 Aug 2007 04:16:11 -0700 (PDT) From: woolly To: users@jackrabbit.apache.org Subject: Re: Using JackRabbit for XML Structures In-Reply-To: <46C5A71B.90109@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: p.barr@lbs-ltd.com References: <12197500.post@talk.nabble.com> <46C5A71B.90109@comcast.net> X-Virus-Checked: Checked by ClamAV on apache.org I've decided to store the xml as jcr:data in an nt:resource node. However, the hierarchy, which contains thousands of nodes, is still huge when stored on the file system (or in a database). Is there a way of reducing the amount of space these nodes take up? Perhaps using a different nodetype? At the moment they all just go in as nt:unstructured. Thanks for you comments. Dan Connelly-3 wrote: > > Phil: > > Try placing your XML document (as jcr:data) in an nt:resource node. > > "Import" assumes you want to have the JCR to access separate elements of > XML directly, as JCR nodes. If, on the other hand, you only want to > fetch the entire XML (as a single document), then nt:resource is a more > economical solution. You can stream the docuemnt and use XPath > to isolate the elements of interest. > > BTW, JBossESB bundles Jackrabbit as its "Message Store". If your > application is running on JBoss, upgrading to JBossESB just for its > Message Store might be an option for you, assuming you do not need a > full-blown Content Management System. JBossESB has less functionality > but gives you a useful, supported, higher-level api for xml storage. > > -- Dan Connelly > > > woolly wrote: >> Hi all, >> >> I'm trying to use JackRabbit to maintain XML documents. The problem is >> that >> these XML documents can get quite large. When I try to import an 8mb >> document, it becomes 180mb in the repository (storing it just on the >> filesystem), and it takes about 5 minutes to go in. >> I'm just using... >> session.importXML(node.getPath(), fis, >> ImportUUIDBehavior.IMPORT_UUID_CREATE_NEW); >> ...to import the xml, where the node is of type nt:unstructured. >> >> Is there a configuration or method that I should be using in order to let >> jackrabbit know that i'm dealing with xml? >> >> Thanks for any help. >> >> Phil. >> > > > -- View this message in context: http://www.nabble.com/Using-JackRabbit-for-XML-Structures-tf4284970.html#a12272534 Sent from the Jackrabbit - Users mailing list archive at Nabble.com.