Hi Robert, the serialization depends on the artifacts of the aggregate. Generic nodes are represented in SerializerArtifacts, which use the DocViewSerializer which use the DocViewSAXFormatter. So DocViewSAXFormatter is probably what you're looking for. Note, there is also a customized XMLSerializer that is used to sort the XML attributes and enforce constant indentation.
Note that the filevault architecture is very abstracted. the idea once was to have a transparent FS layer on top of a JCR repository that also could be accessed via any other (virtual) filesystem like webdav. In the meantime, I believe we should add a much simpler approach that is less complicated and more robust and especially forget about the svn-like operations like vlt ci, vlt co, vlt diff, vlt st. regards, toby On Sat, Aug 17, 2013 at 4:41 AM, Robert Munteanu <[email protected]> wrote: > Hi, > > I'm looking into using FileVault's capabilities for our upcoming Sling > IDE Tooling. My approach is to reuse bits and pieces of FileVault and > plug them into the Eclipse's extension points, rather than delegate to > coarse-grained operations like 'checkout' or 'update workspace'. > > I've tried to locate the area of code which is responsible for > serializing a Node into an XML respresentation - the .content.xml format > - but failed. What part of the code is responsible for representing > Nodes in an XML format? > > Thanks, > > Robert > > >
