From jackrabbit-dev-return-2061-apmail-incubator-jackrabbit-dev-archive=www.apache.org@incubator.apache.org Wed May 18 08:43:29 2005 Return-Path: Delivered-To: apmail-incubator-jackrabbit-dev-archive@www.apache.org Received: (qmail 46306 invoked from network); 18 May 2005 08:43:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 18 May 2005 08:43:29 -0000 Received: (qmail 11231 invoked by uid 500); 18 May 2005 08:43:21 -0000 Mailing-List: contact jackrabbit-dev-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-dev@incubator.apache.org Received: (qmail 11190 invoked by uid 99); 18 May 2005 08:43:20 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from relay.gossinteractive.com (HELO relay.gossinteractive.com) (212.104.154.111) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 18 May 2005 01:43:19 -0700 Received: from delboy.lan.gossinteractive.com ([10.10.10.240]) by relay.gossinteractive.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 18 May 2005 09:44:13 +0100 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Repository Fatal Error Date: Wed, 18 May 2005 09:39:36 +0100 Message-ID: <8D07567F3496FA4797E37564D4B4DC0E8461EB@delboy.lan.gossinteractive.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Repository Fatal Error thread-index: AcVbbKHyoGhpFchFQYSBBPAo8ZcsZgAFjg/Q From: "Simon Gash" To: X-OriginalArrivalTime: 18 May 2005 08:44:13.0964 (UTC) FILETIME=[C4C044C0:01C55B85] X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Thanks for that Edgar, I hadn't really thought much about the choice of persistence manager as in the future I want to move over to a relational database storage. I was hoping to use Apache obj. Is anybody using this yet ? I'm anxious to get some feedback on performance. Thanks Simon -----Original Message----- From: Edgar Poce [mailto:edgarpoce@gmail.com]=20 Sent: 18 May 2005 05:11 To: jackrabbit-dev@incubator.apache.org Subject: Re: Repository Fatal Error Hi simon Simon Gash wrote: > OK I've walked my way through the code and this is what I found. ... > I guess the solution would be to encode the xml on storage (& =3D=20 > &), I did this manually and it worked fine. I'm not sure if I=20 > should be checking the new nodes name to ensure its good XML or=20 > whether JackRabbit should be doing it ? Or how about using the CDATA=20 > to block escape literal text ? I think you shouldn't do any check, it's a bug in the XML PM. One possible fix is to escape the sensitive character ('&'). Or maybe create a DOM document and use XML serialization, I think this would be more secure. If you still want to recover your broken repository you can try the tool I uploaded to JIRA (http://issues.apache.org/jira/browse/JCR-76). It will ask you to remove any reference to nodes and properties that the PM is unable to read. I plan to add a GUI that will let the user navigate the PM, but it's only a console tool for now :(. btw, I don't think XML PM + CQFS is a good choice. xml is human readable but it's no so easy to read/write if it's stored in cqfs. IMHO If you need to use cqfs for performance reasons you should use Object PM instead. regards edgar >=20 > Any thoughts anyone... >=20 > Thanks for your time. >=20 >=20 > Simon Come visit us at: =20 Internet World 2005. June 14 - 16, Earls Court, Stand # A60 Government Computing Expo. June 21 & 22, Earls Court, Stand # 804 SOCITM Annual Event. October 16 - 18 Brighton Hotel, Stand # 28 GOSS - Ranked 4th in the Deloitte Technology Fast 50 Awards 2004 and = 88th in the Deloitte Technology Fast 500 EMEA.=20 This email contains proprietary information, some or all of which may be = legally privileged. It is for the intended recipient only. If an = addressing or transmission error has misdirected this email, please = notify the author by replying to this email. If you are not the intended = recipient you may not use, disclose, distribute, copy, print or rely on = this email.=20 =20 Email transmission cannot be guaranteed to be secure or error free, as = information may be intercepted, corrupted, lost, destroyed, arrive late = or incomplete or contain viruses. This email and any files attached to = it have been checked with virus detection software before transmission. = You should nonetheless carry out your own virus check before opening any = attachment. GOSS Interactive Ltd accepts no liability for any loss or = damage that may be caused by software viruses. =20