[
https://issues.apache.org/jira/browse/OAK-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13235438#comment-13235438
]
Marcel Reutegger commented on OAK-28:
-
Regarding value bindings and query parsing in the
Hi,
OAK-36 covers the Query implementation effort, but I'm wondering if now
would be a good time to mention indexing as well.
We want to have dedicated indexes, I think that would be accomplished via
observation.
Any ideas about the availability of this feature?
Sure. One such a mechanism is
[
https://issues.apache.org/jira/browse/OAK-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13235455#comment-13235455
]
Thomas Mueller commented on OAK-28:
---
Why do we need to implement a query parser in the jcr
[
https://issues.apache.org/jira/browse/OAK-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13235462#comment-13235462
]
Thomas Mueller commented on OAK-36:
---
+1
An implementation detail: Instead of complete query
hi
from some basic discussions at the last f2f in basel i got the
impression that we may have multiple independant JCR repositories
in the same MikroKernel instance.
if that was the case and not a misunderstanding from my side,
i would like us to discuss how those different JCR repositories
are
hi
i would like to discuss the nature of exceptions that will
be thrown from the oak-api/spi module.
to illustrate:
we decided that quite some core functionality of the JCR
API will effectively be executed and validated on the oak-core-layer
such as for example authentication, authorization or
On 22.3.12 10:18, Jukka Zitting wrote:
Hi,
On Thu, Mar 22, 2012 at 11:08 AM, Michael Dürigmdue...@apache.org wrote:
I think this is not the case. If I'm not completely mistaken there will be
always an 1:1 correspondence between an MicroKernel instance and a
Repository instance.
That's my
Hi,
*If* we use unchecked exceptions, by all means let them all extend a
common base exception :-)
I think we should use unchecked exceptions except possibly in the JCR API
itself. As for 'possibly' see http://java.net/jira/browse/JSR_333-14 - I
still hope this will be accepted for JSR 333 :-)
On Wed, Mar 21, 2012 at 8:26 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
Hi,
The MicroKernel interface currently says:
supported property types: string, number
that's outdated, it now says: string, number, boolean
In addition there's explicit support for binary blobs.
For oak-core
On Thu, Mar 22, 2012 at 4:22 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
Hi,
On Thu, Mar 22, 2012 at 3:04 PM, Stefan Guggisberg
stefan.guggisb...@gmail.com wrote:
On Wed, Mar 21, 2012 at 8:26 PM, Jukka Zitting jukka.zitt...@gmail.com
wrote:
For oak-core (see OAK-33 [1]) we'd need a
Hi,
On Thu, Mar 22, 2012 at 4:53 PM, Stefan Guggisberg
stefan.guggisb...@gmail.com wrote:
On Thu, Mar 22, 2012 at 4:22 PM, Jukka Zitting jukka.zitt...@gmail.com
wrote:
Can we turn that into a harder API contract, i.e. one that should hold
true for any MK implementation? If not, we need to
[
https://issues.apache.org/jira/browse/OAK-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13235676#comment-13235676
]
Thomas Mueller commented on OAK-33:
---
About Scalar.getType():
We need some way to represent
[
https://issues.apache.org/jira/browse/OAK-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller updated OAK-34:
--
Description: Define a oak-core API for handling queries. How do we handle
name space mappings, value
Hi,
in other words: the URL use to create the MK instance must not only
identify the store and the workspace but also the repository?
I thought we want to keep the data of all workspaces within the same
physical storage, so use the same MK instance for all workspaces within a
repository.
KernelNodeState should handle multi valued properties
-
Key: OAK-38
URL: https://issues.apache.org/jira/browse/OAK-38
Project: Jackrabbit Oak
Issue Type: Bug
Reporter: Michael
[
https://issues.apache.org/jira/browse/OAK-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13236171#comment-13236171
]
Michael Dürig commented on OAK-33:
--
I committed and initial implementation of Scala in
[
https://issues.apache.org/jira/browse/OAK-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13236171#comment-13236171
]
Michael Dürig edited comment on OAK-33 at 3/22/12 11:27 PM:
I
17 matches
Mail list logo