Hi,
On Thursday, July 19, 2012, Thomas Mueller wrote:
>
> > Š oak-http are the
> > only complex direct Java clients of the Oak API
>
> I thought Oak HTTP basically _is_ (very closely matches) the Oak API.
That's why I qualified it with "to a lesser degree", which you didn't
include in your quote
On 18.07.2012, at 16:17, Jukka Zitting wrote:
> In fact, the more I think of the specific case of the proposed
> ":childOrder" property and orderability of nodes, the more it seems
> that you are right - it is better to hide these details below the Oak
> API and explicitly extend the API with an or
+1 !!!
Cheers,
Alex
On 12.07.2012, at 21:01, Jukka Zitting wrote:
> Hi,
>
> When talking with people interested in Oak, a common complaint (I've
> heard it now from three different sources) is that trying to follow
> the broader design discussions on oak-dev@ is a bit difficult with the
> often
angela created OAK-199:
--
Summary: KernelNodeStore defines 2 access methods for the
CommitEditor
Key: OAK-199
URL: https://issues.apache.org/jira/browse/OAK-199
Project: Jackrabbit Oak
Issue Type: Impro
[
https://issues.apache.org/jira/browse/OAK-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-196:
---
Summary: Make Root interface permission aware (was: Adjust Root interface
permission aware)
> Make Root interface
[
https://issues.apache.org/jira/browse/OAK-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved OAK-198.
Resolution: Fixed
Fix Version/s: 0.4
Committed revision 1363383
> Refactor RootImpl#merge
> --
angela created OAK-198:
--
Summary: Refactor RootImpl#merge
Key: OAK-198
URL: https://issues.apache.org/jira/browse/OAK-198
Project: Jackrabbit Oak
Issue Type: Improvement
Reporter: angela
I
angela created OAK-197:
--
Summary: oak-api ConflictHandler defines method using
oak.spi.state.NodeState
Key: OAK-197
URL: https://issues.apache.org/jira/browse/OAK-197
Project: Jackrabbit Oak
Issue Type
[
https://issues.apache.org/jira/browse/OAK-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-196:
---
Attachment: OAK-196.patch
proposed patch
> Adjust Root interface permission aware
> ---
angela created OAK-196:
--
Summary: Adjust Root interface permission aware
Key: OAK-196
URL: https://issues.apache.org/jira/browse/OAK-196
Project: Jackrabbit Oak
Issue Type: Sub-task
Components
[
https://issues.apache.org/jira/browse/OAK-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418281#comment-13418281
]
angela commented on OAK-160:
Revision: 1363328
Similar to OAK-192, OAK-194, OAK-195 adjusted the
[
https://issues.apache.org/jira/browse/OAK-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418270#comment-13418270
]
Alex Parvulescu commented on OAK-154:
-
revision 1363321
- bumped lucene up to 4.0.0 alph
[
https://issues.apache.org/jira/browse/OAK-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved OAK-195.
Resolution: Fixed
Fix Version/s: 0.4
Revision: 1363323
> State that Tree#hasProperty returns
[
https://issues.apache.org/jira/browse/OAK-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved OAK-194.
Resolution: Fixed
Fix Version/s: 0.4
Revision: 1363323
> Define behavior of Tree#getProperty(
[
https://issues.apache.org/jira/browse/OAK-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved OAK-192.
Resolution: Fixed
Fix Version/s: 0.4
committed revision 1363320
> Define behavior of Tree#getP
[
https://issues.apache.org/jira/browse/OAK-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved OAK-193.
---
Resolution: Fixed
Fix Version/s: 0.4
I added such a class in revision 1363277.
>
[
https://issues.apache.org/jira/browse/OAK-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418206#comment-13418206
]
Jukka Zitting commented on OAK-64:
--
In revision 1363287 I modified the {{registerDefinition()
Hi,
On Thu, Jul 19, 2012 at 11:59 AM, Angela Schreiber wrote:
> oh, i see... i got that wrong since the original mail and the issue
> gave me the impression that there already exists quite some internal
> content.
Right. I wanted to bring this up already now as we're about to start
hitting such
angela created OAK-195:
--
Summary: State that Tree#hasProperty returns false of the property
is not accessible
Key: OAK-195
URL: https://issues.apache.org/jira/browse/OAK-195
Project: Jackrabbit Oak
Iss
hi jukka
thanks for the info.
As you noticed, it's meant for use by plugins that want to access a
raw NodeState through the Tree API without any internal layers
(security, etc.) in between. Ideally such a wrapper wouldn't be
needed, as it mixes levels of abstraction, which is why I didn't want
[
https://issues.apache.org/jira/browse/OAK-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418193#comment-13418193
]
Jukka Zitting commented on OAK-194:
---
I think in that case the method should return {{null}}
hi jukka
was it possible for you to share the known set of special properties
with the team?
See the end of my message from yesterday.
oh, i see... i got that wrong since the original mail and the issue
gave me the impression that there already exists quite some internal
content.
if i und
angela created OAK-194:
--
Summary: Define behavior of Tree#getProperty(String) in case of
lack of access
Key: OAK-194
URL: https://issues.apache.org/jira/browse/OAK-194
Project: Jackrabbit Oak
Issue Typ
Jukka Zitting created OAK-193:
-
Summary: TODO class for partially implemented features
Key: OAK-193
URL: https://issues.apache.org/jira/browse/OAK-193
Project: Jackrabbit Oak
Issue Type: New Feat
Hi,
On Thu, Jul 19, 2012 at 11:26 AM, Stefan Guggisberg
wrote:
> a) in scenarios where the Oak-API is remoted we'll have to buffer transient
> changes on the client and batch-write them to the 'server' (Oak-API impl).
> handling the transient space exclusively below the Oak-API is IMO not
> an op
angela created OAK-192:
--
Summary: Define behavior of Tree#getParent() if the parent is not
accessible
Key: OAK-192
URL: https://issues.apache.org/jira/browse/OAK-192
Project: Jackrabbit Oak
Issue Type:
Hi,
>>> Š oak-http are the
>> > only complex direct Java clients of the Oak API
>>
>> I thought Oak HTTP basically _is_ (very closely matches) the Oak API.
>
>
>That's why I qualified it with "to a lesser degree", which you didn't
>include in your quote above.
I guess this is an example where a d
On Thu, Jul 19, 2012 at 11:09 AM, Jukka Zitting wrote:
> Hi,
>
> On Thu, Jul 19, 2012 at 10:18 AM, Stefan Guggisberg
> wrote:
>> implementing the transient space in Oak-Core is
>> legitimate, although premature optimization for
>> the specific use case where the entire stack
>> (jcr-...-mk) runs
Hi,
>i raised the same issue: OAK-162
I read it, good to know it was already discussed. I basically matches my
concern.
Regards,
Thomas
angela created OAK-191:
--
Summary: ChangeExtractor uses interfaces from oak.spi.state
Key: OAK-191
URL: https://issues.apache.org/jira/browse/OAK-191
Project: Jackrabbit Oak
Issue Type: Bug
Com
[
https://issues.apache.org/jira/browse/OAK-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-190:
---
Component/s: jcr
core
> Use JCR API defined by JSR-333
> --
>
>
Hi,
On Thu, Jul 19, 2012 at 10:18 AM, Stefan Guggisberg
wrote:
> implementing the transient space in Oak-Core is
> legitimate, although premature optimization for
> the specific use case where the entire stack
> (jcr-...-mk) runs in the same vm.
To clarify, the decision to write changes from oak
Hi,
On Thu, Jul 19, 2012 at 10:54 AM, Angela Schreiber wrote:
> was it possible for you to share the known set of special properties
> with the team?
See the end of my message from yesterday.
BR,
Jukka Zitting
angela created OAK-190:
--
Summary: Use JCR API defined by JSR-333
Key: OAK-190
URL: https://issues.apache.org/jira/browse/OAK-190
Project: Jackrabbit Oak
Issue Type: Task
Reporter: angela
t
Hi,
On Thu, Jul 19, 2012 at 10:40 AM, Angela Schreiber wrote:
> - what is the aim of the ReadOnlyTree?
As you noticed, it's meant for use by plugins that want to access a
raw NodeState through the Tree API without any internal layers
(security, etc.) in between. Ideally such a wrapper wouldn't b
hi jukka
i see your point regarding keeping the API as small as possible.
that's basically why i was asking for a list of those special
properties that we already know or envision to introduce.
was it possible for you to share the known set of special properties
with the team?
that would allow
hi all
while working on a initial permission check upon read access in
oak i found that there are two implementations of the Tree interface:
- TreeImpl:
> only used within RootImpl
> package private create method, private constructor
- ReadOnlyTree:
> used in NameValidatorProvider and Nam
Hi,
On Thursday, July 19, 2012, Thomas Mueller wrote:
>
> > Š oak-http are the
> > only complex direct Java clients of the Oak API
>
> I thought Oak HTTP basically _is_ (very closely matches) the Oak API.
That's why I qualified it with "to a lesser degree", which you didn't
include in your quote
[
https://issues.apache.org/jira/browse/OAK-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418161#comment-13418161
]
Jukka Zitting commented on OAK-64:
--
bq. i would appreciate if you would at least state that y
On Thu, Jul 19, 2012 at 9:21 AM, Thomas Mueller wrote:
> Hi,
>
> I believe we have quite different views about what the architecture should
> look like and what the goals of the separation between the layers are. I
> understand the view people have changes as we implement things, but could
> we di
Hi,
I believe we have quite different views about what the architecture should
look like and what the goals of the separation between the layers are. I
understand the view people have changes as we implement things, but could
we discuss the architecture and problems we found in the next meeting? I
41 matches
Mail list logo
