Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Message-ID: <466FC3E2.8090609@comcast.net>
Date: Wed, 13 Jun 2007 06:16:02 -0400
From: Dan Connelly <daniel.s.connelly@comcast.net>
User-Agent: Thunderbird 2.0.0.0 (X11/20070326)
MIME-Version: 1.0
To: users@jackrabbit.apache.org
Subject: Re: Importing and Exporting XML
References: <11082908.post@talk.nabble.com>
In-Reply-To: <11082908.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

woolly:

The term "DocumentView" is slightly misleading.    Its more like a 
Shredded And Annotated Document View.

The xml document will get shredded into its constituent element nodes 
when you import it as "DocumentView".   This import will not store a 
single, coherent document in the Repository.    WebDav support in 
Jackrabbit, on the other hand, can be used to store the document as 
coherent text.     Customized, hybrid approaches are possible to support 
structured content (partial shredding over WebDav).  It depends on your 
use case how much (or how little) shredding you want.

The metadata gets added to raw shreds during DocumentView import to 
indicate the Jackrabbit element node type structure.    By default, node 
type will be nt:unstructured on raw nodes (not having metadata 
already).   You can write a simple XSLT to strip out the metadata when 
you export.   For import you can work this in reverse and add a custom 
structure using XSLT (but that may not be simple).

It sounds like your use case (customized node editing) requires some 
custom node types.   This can work nicely if the set of element tags is 
limited and fixed.   Also, you probably also will need to add some 
custom xml processing (dom, sax or xslt).

What xml editor are you using?   I think XML Spy has integration 
features that would support partial shredding and customized document 
views.   (But, I have never worked this.)

    -- Dan Connelly


woolly wrote:
> Hi all,
>
> Is it possible to import xml into a node, and then export that xml back out
> to have the same xml-equivalent file? At the moment I'm trying:
>
> fis = new FileInputStream(inputFile);
> session.importXML(node.getPath(), fis,
> ImportUUIDBehavior.IMPORT_UUID_CREATE_NEW);
> fis.close();
>
> // followed by....
> out = new FileOutputStream(outputFile);
> session.exportDocumentView(node.getPath(), out, true, false);
>
> The difference between inputFile and outputFile seems to be that there are
> some additional jcr specific attributes. Is this necessary?
>
> What I'm really trying to do is manage an xml document (eventually many xml
> documents), allow people to make changes to only certain parts of it,
> versioning those parts and using other JackRabbit features. Is this the kind
> of thing that JackRabbit was intended for? Or should I just load the xml
> document in as a property of a node and deal with the other things myself?
>
> Thanks for any help,
>
> Phil.
>