jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jackrabbit Wiki] Update of "JackrabbitFileVaultFS" by TobiasBocanegra
Date Wed, 04 Sep 2013 00:46:07 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The "JackrabbitFileVaultFS" page has been changed by TobiasBocanegra:

   extendable:: A plugin mechanism should allow to extend the mapping layer for further conversions
filters and aggregators.
  == Overview ==
- <img style="float:right" src="%topic.attachments%/vaultfs.png" />
+ {{attachment:vaultfs.png}}
  !VaultFs consists mainly of 2 layers that map the repository's nodes to !VaultFs files:
The '''Aggregate Node Tree''' that is managed by the ''aggregate manager'' represents a hierarchical
view of the content aggregates. Each aggregate is addressed by a path and allows access to
its artifacts. The artifacts nodes are built using ''aggregators'' that define which repository
items belong to an aggregate and what artifacts they produce. For each artifact there is a
''serializer'' defined that is used to export and import the respective content. 
  On top of the aggregate tree is the '''Vault File System''' that accesses the aggregates
and exposes them as tree of ''vault files''. They can be used to export and import the actual
repository content. The mapping from aggregates and its artifacts to vault files is done in
an intuitive way so that clients (and users) can deal with them in a natural filesystem like
- {{%topic.attachments%/vault_sample.png|Example Tree}}
+ {{attachment:vault_sample.png}}
  == Aggregate Manager ==
  The aggregate manager is configured with a set of aggregators and serializers. Once the
manager is mounted on a jcr repository it exposes a tree of aggregates. They are collected
using an aggregator that matches the respective repository node. For example the ''nt:file
aggregator'' produces an artifacts node that allows no further child nodes and provides (usually)
one primary artifact (which represents the content of the file).

View raw message