Hi Phil, I think you may be looking for what's called an XML DocumentView import.
This allows you to deal with your XML document on an XML-element/attribute level, when it comes to content repository features such as versioning, locking or query. regards, david On 10/2/07, woolly <[EMAIL PROTECTED]> wrote: > > Hi all, > > I have recently had a problem where I was trying to import a large xml > document into the jackrabbit repository. The repository expanded hugely > during import. I solved this problem by having some elements of the xml > stored as an nt:resource node (as jcr:data with an xml mimetype). > > Now I've got the problem that I want repository features such as versioning > and referencing to apply to some parts of the xml that is stored in the > nt:resource. Does anyone have any ideas on the best way to implement this? > I'm thinking about taking the xml chunk I want to version out of the > nt:resource and then storing it somewhere else. But then, what's the best > way of making the link between the nt:resource xml and the new "exploded" > xml? > > Is there a better way to allow repository features to apply to parts of xml > stored in an nt:resource? > > Thanks for any help, > > Phil. > > -- > View this message in context: > http://www.nabble.com/CMS-Functionality-In-An-nt%3Aresource---tf4554191.html#a12996511 > Sent from the Jackrabbit - Users mailing list archive at Nabble.com. > >
