Comments on: JCR Woes http://www.symphonious.net/2007/06/28/jcr-woes/ Living in a state of accord. Tue, 07 Feb 2012 01:07:58 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Rob@Rojotek » Blog Archive » TDD With JackRabbithttp://www.symphonious.net/2007/06/28/jcr-woes/comment-page-1/#comment-95368 Rob@Rojotek » Blog Archive » TDD With JackRabbit Fri, 29 Jun 2007 00:20:10 +0000 https://www.symphonious.net/2007/06/28/jcr-woes/#comment-95368 [...] AJ mentioned, we are currently working with Apache JackRabbit for an internal project.  It has been an [...] [...] AJ mentioned, we are currently working with Apache JackRabbit for an internal project.  It has been an [...]

]]> By: Jukka Zittinghttp://www.symphonious.net/2007/06/28/jcr-woes/comment-page-1/#comment-95349 Jukka Zitting Thu, 28 Jun 2007 21:48:52 +0000 https://www.symphonious.net/2007/06/28/jcr-woes/#comment-95349 Do you use system view for the XML export? See https://issues.apache.org/jira/browse/JCR-674 for a bug report related to invalid XML characters and a potential fix that should be there for the system view format in the latest releases (seems like the bug wasn't properly marked as resolved, I'll check the status). Let me know if there's something else you need. Ode, the original filesystem persistence options were early development versions. All the official Jackrabbit releases have used an embedded Derby database as the default persistence mechanism. Do you use system view for the XML export? See https://issues.apache.org/jira/browse/JCR-674 for a bug report related to invalid XML characters and a potential fix that should be there for the system view format in the latest releases (seems like the bug wasn’t properly marked as resolved, I’ll check the status). Let me know if there’s something else you need.

Ode, the original filesystem persistence options were early development versions. All the official Jackrabbit releases have used an embedded Derby database as the default persistence mechanism.

]]> By: Adrian Suttonhttp://www.symphonious.net/2007/06/28/jcr-woes/comment-page-1/#comment-95338 Adrian Sutton Thu, 28 Jun 2007 21:23:42 +0000 https://www.symphonious.net/2007/06/28/jcr-woes/#comment-95338 Odi, Yeah it's not proving too wonderful for us. The content should have been base64 encoded and looked like it was, but clearly it hadn't been done properly. Odi,
Yeah it’s not proving too wonderful for us. The content should have been base64 encoded and looked like it was, but clearly it hadn’t been done properly.

]]> By: Odihttp://www.symphonious.net/2007/06/28/jcr-woes/comment-page-1/#comment-95247 Odi Thu, 28 Jun 2007 07:46:14 +0000 https://www.symphonious.net/2007/06/28/jcr-woes/#comment-95247 Uh Jackrabbit... Reminds me badly of my Magnolia experiences... Does it still store everything in a hashed filesystem? I don't understand why they didn't use a DB as a backend. It's insane to use the fs for that. Try and take a consistent online snapshot for backup purposes? Errm... sorry, mate. Try and fix a broken repository by hand. Well, errm... now where do I start exactly? On top of that we had a huge file handle leak, but that may have been Magnolia's fault - who knows. As for binary content in XML: you must Base64 encode it. Even if was a legal character (I don't know if it is), I expect parsers written in C to treat it as EOF :-) Uh Jackrabbit… Reminds me badly of my Magnolia experiences… Does it still store everything in a hashed filesystem? I don’t understand why they didn’t use a DB as a backend. It’s insane to use the fs for that. Try and take a consistent online snapshot for backup purposes? Errm… sorry, mate. Try and fix a broken repository by hand. Well, errm… now where do I start exactly? On top of that we had a huge file handle leak, but that may have been Magnolia’s fault – who knows.

As for binary content in XML: you must Base64 encode it. Even if was a legal character (I don’t know if it is), I expect parsers written in C to treat it as EOF :-)

]]>