[jira] [Updated] (OAK-130) Unexpected result of MicroKernel#getJournal after MicroKernel#merge

[ https://issues.apache.org/jira/browse/OAK-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Guggisberg updated OAK-130: -- Summary: Unexpected result of MicroKernel#getJournal after MicroKernel#merge (was: Unexpected beh

[jira] [Created] (OAK-140) PropertyState: data type of empty array property

Thomas Mueller created OAK-140: -- Summary: PropertyState: data type of empty array property Key: OAK-140 URL: https://issues.apache.org/jira/browse/OAK-140 Project: Jackrabbit Oak Issue Type: Imp

[jira] [Updated] (OAK-139) Remove JsonBuilder

[ https://issues.apache.org/jira/browse/OAK-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-139: -- Attachment: OAK-139.patch Proposed patch > Remove JsonBuilder > -- > >

[jira] [Created] (OAK-139) Remove JsonBuilder

Michael Dürig created OAK-139: - Summary: Remove JsonBuilder Key: OAK-139 URL: https://issues.apache.org/jira/browse/OAK-139 Project: Jackrabbit Oak Issue Type: Bug Components: core

[jira] [Comment Edited] (OAK-138) Move client/server package in oak-mk to separate project

[ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294428#comment-13294428 ] Thomas Mueller edited comment on OAK-138 at 6/13/12 12:59 PM: -- O

[jira] [Commented] (OAK-138) Move client/server package in oak-mk to separate project

[ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294428#comment-13294428 ] Thomas Mueller commented on OAK-138: OK, my personal opinion is still to use as few proje

[jira] [Commented] (OAK-138) Move client/server package in oak-mk to separate project

[ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294393#comment-13294393 ] Thomas Mueller commented on OAK-138: I understand this issue is about remoting. However,

[jira] [Commented] (OAK-138) Move client/server package in oak-mk to separate project

[ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294366#comment-13294366 ] Dominique Pfister commented on OAK-138: --- @Thomas: I agree that other MK implementations

[jira] [Commented] (OAK-138) Move client/server package in oak-mk to separate project

[ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294318#comment-13294318 ] Thomas Mueller commented on OAK-138: The data store that is currently in oak-mk (org.apac

[jira] [Commented] (OAK-138) Move client/server package in oak-mk to separate project

[ https://issues.apache.org/jira/browse/OAK-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294307#comment-13294307 ] Stefan Guggisberg commented on OAK-138: --- > It also contains the MicroKernel API itself.

Re: NodeDelegate leakage from NodeImpl

On 13.6.12 8:04, Thomas Mueller wrote: Hi, This defeats the original intent of the separation of NodeImpl and NodeDelegate (OAK-84) users should not be able to gain access to internals by hacking NodeImpl. Hm, is this a security problem? Do we want to protect the data from users of the JCR

Re: NodeDelegate leakage from NodeImpl

Hi, > This defeats the original intent of the > separation of NodeImpl and NodeDelegate (OAK-84) > users should not be able to gain access to internals by hacking NodeImpl. Hm, is this a security problem? Do we want to protect the data from users of the JCR API? Or do we want to protect the dat