My goal is to compare jackrabbit to our current configuration of using slide, and hopefully be able to just replace slide with little code change/impact on code, and hopefully improve performance.

We currently run slide under jetty and store xml, png, jgp, txt, and one dtd file in the repository.

I set up a brand new install of Jetty, I added jackrabbit to jetty, then created a new repository using the standard jackrabbit-webapp-1.4 webapp. I then checked out everything from our current slide repository using cadaver, and then added all these files into jackrabbit, again using cadaver.

I did it this way so that I could write a script, using cadaver, to checkout all the files from the slide repository and from the jackrabbit repository, and compare how long each took to perform this action. slide currently performs a complete get of all the files in roughly 35 seconds, jackrabbit takes nearly 10 minutes, and I can see from the logs that the snag is on the larger xml files.

That said, I had never used WEBDAV until a week ago, I am new to all this, another developer did the initial implementation of slide in our product. So I am new to this, and my be hopping down the wrong bunny trail (sorry for the pun), or asking the wrong questions. I just want/ need jackrabbit to work via WEBDAV as good/better than slide can now, so that we can replace slide with jackrabbit.

We prefer to stick with derby for the database, we like that approach. If I can tweak something in the repository.xml to have jackrabbit treat xml/everything as binary, that is fine, or if I need to write a custom importer in java to check everything in in binary, that is fine too. I am just looking for the correct answer.

Does this make sense?

Thanks, Wade

On Jun 5, 2008, at 10:26 AM, Alexander Klimetschek wrote:

Sorry, I don't know about cadaver. The "normal" behaviour with Webdav
should be that imported files are stores as nt:file. But that can be
customized. Is there any specific configuration of the Webdav in your
Jackrabbit server?

Alex

On Thu, Jun 5, 2008 at 4:03 PM, Wade Girard <[EMAIL PROTECTED]> wrote:
I see the confusion (with me)! myfile/jcr:content/jcr:data set when
setting/getting the Node property in java, I am using cadaver to put/get
files from a command line to jackrabbit via the WEBDAV interface.

I have only been doing this for a few days now, can I set this somehow using cadaver? Or is there a way to tell jackrabbit to treat xml files this way
through the repository.xml?

Thanks

On Jun 5, 2008, at 8:43 AM, Alexander Klimetschek wrote:

Put the serialized XML stream into a binary property:
myfile/jcr:content/jcr:data (where myfile is of type nt:file and
jcr:content is of nt:resource).

See also the JCR spec for more info on nt:file/nt:folder and nt:resource.

Alex

On Thu, Jun 5, 2008 at 3:25 PM, Wade Girard <[EMAIL PROTECTED]>
wrote:

okay, I see this:

If you need to store XML documents as-is (as opposed to an abstract
content model that's just serialized to XML), then I would recommend
storing the XML as a binary property, preferably inside a
nt:file/nt:resource structure.

How do I do this?

On Jun 4, 2008, at 5:58 PM, Alexander Klimetschek wrote:

On Wed, Jun 4, 2008 at 10:55 PM, Wade Girard <[EMAIL PROTECTED] >
wrote:

No, These are all xml files ranging in size from 776 kb to 4 kb

Are you importing the XML content as node structures? See this mail
for a possible improvement:
http://markmail.org/message/uebgv5co6qxxgfff

Regards,
Alex

--
Alexander Klimetschek
[EMAIL PROTECTED]

Wade Girard
[EMAIL PROTECTED]


--
Alexander Klimetschek
[EMAIL PROTECTED]

Wade Girard
[EMAIL PROTECTED]









--
Alexander Klimetschek
[EMAIL PROTECTED]

Day JCR Cup 08 | Win a MacBook Pro: http://dev.day.com/ <<

----------------------------< [EMAIL PROTECTED] >----------
Alexander Klimetschek, Day Management AG, Barfuesserplatz 6,
CH - 4001 Basel, T +41 61 226 55 31, M +49 151 15 77 20 56
---------------------------------------< http://www.day.com >-----------------

Xing: http://www.xing.com/go/invite/3268380.32d2d4
LinkedIn: http://www.linkedin.com/in/klimetschek
Blog: http://weblogs.goshaky.com/weblogs/alexkli/

Wade Girard
[EMAIL PROTECTED]





Reply via email to