Hi, On Tue, Sep 9, 2014 at 5:02 AM, Mathijs den Burger <[email protected]> wrote: > Hi Toby, > > The import code is something along the lines of: > > private void importArchive(final Session session, final Archive > archive, final ImportMode mode) throws ... { > archive.open(true); > > ImportOptions options = new ImportOptions(); > options.setImportMode(mode); > > Importer importer = new Importer(options); > importer.run(archive, <some JCR node>); > } > > The archive implementations override getMetaInf to return some static setup: > > class MyArchive extends AbstractArchive { > > @Override > public MetaInf getMetaInf() { > DefaultMetaInf metaInf = new DefaultMetaInf(); > metaInf.setSettings(VaultSettings.createDefault()); > > DefaultWorkspaceFilter includeAll = new DefaultWorkspaceFilter(); > includeAll.add(PathFilterSet.INCLUDE_ALL); > metaInf.setFilter(includeAll); > > return metaInf; > } > how you you actually provide the files for the archive?
> But it seems the Importer is simply the wrong corner of FileVault to > use when I want to keep a local directory in sync. AFAICS the Importer > is only used in the context of installing Packages. well, but that's exactly what you want. the package manage is specifically built to "assemble" packages that look like a zip of a vlt checkout. and it also allows for installing packages that are built that way. as you might know, we moved the entire vlt/packaging stuff from the day/adobe code into jackrabbit. "we" still use the package manager for all our content deployment and development. we also use maven plugins to create and install packages automatically. I wanted to progress with the donation a long time ago, and finish the http api for the package manager, and also make the maven plugins public. but I hadn't have time yet. > I'm going to try > the Mounter now to 'mount' a part of the local filesystem in a > repository, which then gives me access to a VaultFileSystem in which a > can start a Transaction. ok. regards, toby
