Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 86420 invoked from network); 12 Jun 2008 08:50:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Jun 2008 08:50:59 -0000 Received: (qmail 54076 invoked by uid 500); 12 Jun 2008 08:51:01 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 53943 invoked by uid 500); 12 Jun 2008 08:51:01 -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 53932 invoked by uid 99); 12 Jun 2008 08:51:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jun 2008 01:51:01 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of stefan.guggisberg@gmail.com designates 209.85.198.229 as permitted sender) Received: from [209.85.198.229] (HELO rv-out-0506.google.com) (209.85.198.229) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jun 2008 08:50:12 +0000 Received: by rv-out-0506.google.com with SMTP id k40so4050167rvb.31 for ; Thu, 12 Jun 2008 01:50:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=y5Cbp9TTWS6HADTcjBPQn6nY6oWUjrh1QrWof2gWs54=; b=TZLcTJ3Xb01BKKXb1udI0T2TAOZdvt4AtqYFYWvyJ/c5eMMlamEYKkLUX6nl7GKGbl +PHDKufS467Agb71ew9CM9+8MBNwaTii+dRcsssOAUie/9dFZ3v8XMK2oo+QZIpMuyNY SkDqTtEEtSinZO1xtHeSmo3y2yszUAAE9BPdM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=UZJFxhTDgZeEJfcR7skgZLGwz4Y5iZcVas9OAZ7ggqmU9Uax8Co+A2zCVawq9i0Z90 7iKtd2eKs3guvqbAA6qZA3EdjbUWAEAa5xq4MzCRdI6U2diBOI/HDvdNTA9Evh7K/v+d ai7SxMJPOQMgd2FEgnBOnPcex2LI1axN0JzfI= Received: by 10.114.146.1 with SMTP id t1mr1132899wad.76.1213260629902; Thu, 12 Jun 2008 01:50:29 -0700 (PDT) Received: by 10.114.190.14 with HTTP; Thu, 12 Jun 2008 01:50:29 -0700 (PDT) Message-ID: <90a8d1c00806120150y2e5686fcs97cc57476fdf6f01@mail.gmail.com> Date: Thu, 12 Jun 2008 10:50:29 +0200 From: "Stefan Guggisberg" Sender: stefan.guggisberg@gmail.com To: users@jackrabbit.apache.org Subject: Re: special characters - Migrating to BundlePersistanceManager - Export/Import In-Reply-To: <4850E2AF.6030006@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <485003E4.8030208@gmx.de> <1215798166.20080611202503@holeczek.de> <4850E2AF.6030006@gmx.de> X-Google-Sender-Auth: ea8d970b9ec5a488 X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Jun 12, 2008 at 10:47 AM, Sandro B=F6hme wro= te: > Hi Florian, > > thanks for your feedback! You are probably right. This seems to be the on= ly > solution. have you considered cloning an existing workspace to a new one using Bundle= DbPM? cheers stefan > > Best regards, > > Sandro > > Florian Holeczek schrieb: >> >> Hi Sandro, >> >> what about the brute force solution... iterating over all nodes, >> retrieving their properties content into the corresponding Java >> objects and doing your search in these? >> >> Regards, >> Florian >> >> Urspr=FCngliche Nachricht vom 11.06.2008 um 18:57: >>> >>> Hello, >> >>> currently we are trying to export the content from one repository to >>> another (in this case for migrating to the BundlePersistanceManager). T= he >>> problem is, that our repository contains special characters like #x0d, = #x0a, >>> #x04. As of JCR-674 [1] the export seems to work but the import does no= t >>> decode the base64 encoded values [2]. Our initial thought was, to just >>> remove some of these chars. But it doesn't seem to >>> be possible to create a search query to find these chars. It would just >>> be good for us to know if this is correct, or if we missed something. W= e >>> are depending on preserving the uuids across the repositories so the on= ly >>> way seems to be JCR export/import. >>> At the moment we are in a situation where we cannot migrate to the othe= r >>> PM and cannot use the JCR export/import in general with Jackrabbit. Doe= s >>> somebody know an other way of fixing such content in the repository or >>> exporting/importing it? Any hint is much appreciated. >> >>> Best regards, >> >>> Sandro >> >>> [1] - String properties with invalid XML characters export as invalid X= ML >>> https://issues.apache.org/jira/browse/JCR-674 >> >>> [2] - JCR-1228 Support xs:base64Binary values in system view import >>> https://issues.apache.org/jira/browse/JCR-1228 > >