Hi Nicolas, Versioning won't be part of the picture (at least for now). The export only consists of the modified node(s) and their properties, so the import will also be limited in scope. Of course I am willing to relax these constraints if required.
Thanks for the quick response! -- Mike > -----Original Message----- > From: Nicolas [mailto:[EMAIL PROTECTED] > Sent: Monday, October 16, 2006 12:14 PM > To: users@jackrabbit.apache.org > Subject: Re: Using importXML with existing content > > Hi, > > A first issue is versioning? > > Are you exporting your workspace from the root node? > > On 10/16/06, Daglian, Michael (IT) <[EMAIL PROTECTED]> > wrote: > > > > Hi everyone, > > > > Apologies if this has been answered somewhere before but I couldn't > > find anything via my searching. I was wondering how I could > go about > > using the import xml mechanisms to update the state of one > repository > > into another. My scenario is pretty simple: two Jackrabbit > instances > > each with the same content. When one gets updated I would > like to ship > > out system-view xml to the other and keep it in sync. I would have > > assumed that the UUID collision behavior could be used to > > remove/replace the existing content in the backup but > > org.apache.jackrabbit.core.xml.WorkspaceImporter throws an > > ItemExistsException if content of the same name is imported without > > consulting the UUID behavior flag. Does the spec outline > the behavior > > in this scenario? Is there a recommended in approach for > this sort of > > use case? Thanks in advance! > > > > Best Regards, > > > > -- Mike > > -------------------------------------------------------- > > > > NOTICE: If received in error, please destroy and notify > sender. Sender > > does not intend to waive confidentiality or privilege. Use of this > > email is prohibited when received in error. > > > > > > -- > a+ > Nico > my blog! http://www.deviant-abstraction.net !! > -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.
