jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Guggisberg <stefan.guggisb...@gmail.com>
Subject Re: contrib/jcr-ext proposal
Date Mon, 07 Feb 2005 10:36:27 GMT
On Fri, 04 Feb 2005 17:46:25 +0200, Jukka Zitting <jukka@zitting.name> wrote:

>    o.a.j.ext.xml - XML import/export support
>      Utility classes that implement the XML import/export functionality
>      of JCR using the standard JCR Node API. (Jackrabbit implements
>      similar support classes, but they operate below the JCR API.)
>      Makes it easy for JCR implementations to support the XML operations
>      once the basic Node read/write functionality exists.

i rewrote the export methods as they were moved from Workspace to
Session. the latest implementation internally uses NodeImpl &
PropertyImpl rather than Node & Property
for reasons of performance & simplicity: i wanted to avoid extensive &
redundant String->QName parsing. it will be trivial to change the code
to just use the standard
jcr api to make it generic. but for jackrabbit i don't see the point
in doing so.

regarding the import methods:  i agree with david and doubt that you can 
implement those methods just using the jcr api:
1) Workspace.importXML & getContentHandler need to circumvent the transient
layer and need to write directly to the workspace layer; that's not possible
with the jcr api
2) the semantics of the uuidBehavior flag will be hard if not impossible to
implement correctly just using the jcr api


View raw message