Re: oak-core vs JSON
On 2015-01-05 10:11, Thomas Mueller wrote: Hi, oak.commons.json is currently also used in MicroKernelImpl, and the persistent cache in the DocumentNodeStore. In my experience, the classes JsopBuilder, JsopTokenizer, and JsopStream are much faster and need less memory than org.json.simple, because they use low level streaming, and not a 1:1 JSON-object-to-Java-object representation. JsonObject (which Yes, that's one of the reasons why I stopped using org.json.simple for serialization. does support that) is only used for testing; I guess that class could be moved to the test module. 1) Is oak.commons.json supposed to support all of JSON? Yes. But actually I don't understand why you ask the question. Do you want to interface with another JSON tool? I just don't want to bind me to something that is not a proper JSON implementation :-)- 2) If I switch the RDB code to use it, would it be ok to extend/tune it to meet my specific requirements (with respect to APIs), when needed? What is missing? I think whatever is needed (for high performance JSON processing) should already be there. OK; thanks for confirming; I'll have a closer look then. Best regards, Julian
Re: Oak newbie question re. full versioning, branches, merges
Hi, On 03/01/15 00:01, John Gretz jgre...@yahoo.com.INVALID wrote: Since Oak supports only a single workspace but has capability of full versioning (and lacks simple versioning), how does full versioning work in this context? it means you can use version related operations that are limited to a single workspace. E.g. cross workspace operations are not supported. Under what circumstances can one create a branch and how would that branch be merged (given that the merge-related ops of the VersionManager are not operational in Oak)? the repository creates a branch automatically, when you restore a previous version and then perform a check in. changes from a branch cannot be merged because this is not yet implemented. see also: http://jackrabbit.apache.org/oak/docs/differences.html#Versioning Regards Marcel
Re: oak-core vs JSON
Hi, oak.commons.json is currently also used in MicroKernelImpl, and the persistent cache in the DocumentNodeStore. In my experience, the classes JsopBuilder, JsopTokenizer, and JsopStream are much faster and need less memory than org.json.simple, because they use low level streaming, and not a 1:1 JSON-object-to-Java-object representation. JsonObject (which does support that) is only used for testing; I guess that class could be moved to the test module. 1) Is oak.commons.json supposed to support all of JSON? Yes. But actually I don't understand why you ask the question. Do you want to interface with another JSON tool? 2) If I switch the RDB code to use it, would it be ok to extend/tune it to meet my specific requirements (with respect to APIs), when needed? What is missing? I think whatever is needed (for high performance JSON processing) should already be there. Regards, Thomas On 02/01/15 15:20, Julian Reschke julian.resc...@gmx.de wrote: Hi there, we currently use two libraries for JSON inside oak-core: a) oak.commons.json b) org.json.simple In the RDB code, I currently use org.json.simple for parsing, and custom code for serialization (because it made a significant difference some tests). I assume that I *should* be using oak.commons.json, but back when I looked at this ~12 months ago, it seemed to be specific to JSOP, not necessarily supporting all of JSON. Questions: 1) Is oak.commons.json supposed to support all of JSON? 2) If I switch the RDB code to use it, would it be ok to extend/tune it to meet my specific requirements (with respect to APIs), when needed? Best regards, Julian
jackrabbit-oak build #5071: Fixed
Build Update for apache/jackrabbit-oak - Build: #5071 Status: Fixed Duration: 5326 seconds Commit: 8abd3841fc2d223dc23ecad7f7cd792327a95cb5 (trunk) Author: Julian Reschke Message: OAK-2376: refactoring git-svn-id: https://svn.apache.org/repos/asf/jackrabbit/oak/trunk@1649572 13f79535-47bb-0310-9956-ffa450edef68 View the changeset: https://github.com/apache/jackrabbit-oak/compare/eca97a2572a8...8abd3841fc2d View the full build log and details: https://travis-ci.org/apache/jackrabbit-oak/builds/45991774 -- sent by Jukka's Travis notification gateway
