Re: svn commit: r1305860 - in /jackrabbit/oak/trunk: oak-core/ oak-core/src/main/java/org/apache/jackrabbit/oak/api/ oak-core/src/main/java/org/apache/jackrabbit/oak/api/impl/ oak-jcr/src/main/java/or

2012-03-28 Thread Angela Schreiber
hi michi thanks for commenting. very much appreciated. I added the removed tests back and marked them as ignored. I think we should keep them for the time being until we have the same coverage from another test suite. We can then decide what to do with them. thanks... that's obviously better

[jira] [Created] (OAK-40) Define session-info like user identification for communication with oak-api

2012-03-28 Thread angela (Created) (JIRA)
Define session-info like user identification for communication with oak-api --- Key: OAK-40 URL: https://issues.apache.org/jira/browse/OAK-40 Project: Jackrabbit Oak

Re: svn commit: r1305860 - in /jackrabbit/oak/trunk: oak-core/ oak-core/src/main/java/org/apache/jackrabbit/oak/api/ oak-core/src/main/java/org/apache/jackrabbit/oak/api/impl/ oak-jcr/src/main/java/or

2012-03-28 Thread Michael Dürig
On 28.3.12 7:50, Angela Schreiber wrote: + + /** + * Returns the current revision the associated session is operating on. + * Upon creation of a given {@code SessionInfo} instance the initial + * revision is always set to the head revision. Upon successful commit + * of changes the revision is

[jira] [Created] (OAK-41) Initial repository setup

2012-03-28 Thread angela (Created) (JIRA)
Initial repository setup Key: OAK-41 URL: https://issues.apache.org/jira/browse/OAK-41 Project: Jackrabbit Oak Issue Type: Task Components: core Reporter: angela upon the initial creation of

Re: svn commit: r1306222 - in /jackrabbit/oak/trunk/oak-jcr/src: main/java/org/apache/jackrabbit/oak/jcr/ main/java/org/apache/jackrabbit/oak/jcr/query/ test/java/org/apache/jackrabbit/oak/jcr/ test/j

2012-03-28 Thread Michael Dürig
Hi Tom, On 28.3.12 10:11, thom...@apache.org wrote: Author: thomasm Date: Wed Mar 28 09:11:39 2012 New Revision: 1306222 URL:http://svn.apache.org/viewvc?rev=1306222view=rev Log: OAK-28 Query implementation (initial implementation of the relevant oak-jcr part) [...] +/** + * The

Re: svn commit: r1306222 - in /jackrabbit/oak/trunk/oak-jcr/src: main/java/org/apache/jackrabbit/oak/jcr/ main/java/org/apache/jackrabbit/oak/jcr/query/ test/java/org/apache/jackrabbit/oak/jcr/ test/j

2012-03-28 Thread Thomas Mueller
Hi, Could you come up with an implementation which does not directly depend on the Microkernel but rather uses a (to be defined) API on oak-core? Sure, let's define such an API. I'm in the process of removing all dependencies from oak-jcr to oak-mk (OAK-20) so this will ultimately break. Sure.

oak api : initial draft

2012-03-28 Thread Angela Schreiber
hi all jukka and myself just were sitting together to define an very first draft of the oak-api just to have something to start with and to have a basis for further discussions. i will commit it as soon as i run the build without error. it will consist of an initial Service that provides -

Re: oak api : initial draft

2012-03-28 Thread Michael Dürig
Great! I was just about to start working on this since this is also a prerequisite for getting OAK-20 resolved. I'll have a look at the draft and let you know. Michael On 28.3.12 15:11, Angela Schreiber wrote: hi all jukka and myself just were sitting together to define an very first

Re: oak api : initial draft

2012-03-28 Thread Angela Schreiber
hi michi just as an additional side note: the conversation between jukka and myself also included some first ideas on how a given repository is being created, who is being in charge of the initial setup and creating the mk and the service instance and how once the repository exists a new

Re: oak api : initial draft

2012-03-28 Thread Michael Dürig
Hi, Some initial comments to the API draft below: SessionInfo.dispose(): do we need this? To me SessionInfo looks like a state less data object (i.e. a value) carrying information related to a user's session. I think we should try to not associate any resources to be disposed with this.

Re: oak api : initial draft

2012-03-28 Thread Angela Schreiber
hi michi ui, that was fast :) SessionInfo.dispose(): do we need this? To me SessionInfo looks like a state less data object (i.e. a value) carrying information related to a user's session. well, i am quite sure that i need it once i have a real authentication mechanism associated with it.

Re: oak api : initial draft

2012-03-28 Thread Michael Dürig
SessionInfo.dispose(): do we need this? To me SessionInfo looks like a state less data object (i.e. a value) carrying information related to a user's session. well, i am quite sure that i need it once i have a real authentication mechanism associated with it. and once a session is logged out

Re: oak api : initial draft

2012-03-28 Thread Michael Dürig
Hi, Some more things that crossed my mind: - Is it possible to open multiple Connection instances with one SessionInfo? What would be the purpose of this? Can I commit a NodeState created with a NodeBuilder from one Connection into another Connection? - Wouldn't it be simpler and

Re: oak api : initial draft

2012-03-28 Thread Jukka Zitting
Hi, On Wed, Mar 28, 2012 at 9:13 PM, Michael Dürig mdue...@apache.org wrote: - Is it possible to open multiple Connection instances with one SessionInfo? What would be the purpose of this? Can I commit a NodeState created with a NodeBuilder from one Connection into another Connection? -

Re: oak api : initial draft

2012-03-28 Thread Jukka Zitting
Hi, On Wed, Mar 28, 2012 at 8:52 PM, Michael Dürig mdue...@apache.org wrote: well, i am quite sure that i need it once i have a real authentication mechanism associated with it. and once a session is logged out i would like to make sure that the session info associated with it is aware of

Re: oak api : initial draft

2012-03-28 Thread Michael Dürig
On Mar 28, 2012 8:52 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Wed, Mar 28, 2012 at 9:13 PM, Michael Dürig mdue...@apache.org wrote: - Is it possible to open multiple Connection instances with one SessionInfo? What would be the purpose of this? Can I commit a NodeState

Re: oak api : initial draft

2012-03-28 Thread Michael Dürig
On Mar 28, 2012 9:27 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Wed, Mar 28, 2012 at 8:52 PM, Michael Dürig mdue...@apache.org wrote: well, i am quite sure that i need it once i have a real authentication mechanism associated with it. and once a session is logged out i would