Hi,
From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
On Tue, Dec 4, 2012 at 2:02 PM, Marcel Reutegger mreut...@adobe.com
wrote:
this implies that oak-jcr supports non-trivial node type modification. do
we really want to go there? to me this sounds like opening pandorra's
box :-/
From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
On Wed, Dec 5, 2012 at 9:19 AM, Marcel Reutegger mreut...@adobe.com
wrote:
I guess in the end I can live with either approach, but right now prefer
1). maybe the tie-breaker could be the question how we actually want to
expose the
Hi,
On Tue, Dec 4, 2012 at 2:02 PM, Marcel Reutegger mreut...@adobe.com wrote:
this implies that oak-jcr supports non-trivial node type modification. do
we really want to go there? to me this sounds like opening pandorra's
box :-/
No, oak-jcr doesn't need to support any such things. But it
Hi,
From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
On Thu, Nov 29, 2012 at 3:11 PM, Marcel Reutegger
mreut...@adobe.com wrote:
now, to implement the various JCR versioning operations, I'd like
to encapsulate them in commit hooks as much as possible. this
avoid the need to duplicate
Hi,
On Thu, Nov 29, 2012 at 3:11 PM, Marcel Reutegger mreut...@adobe.com wrote:
...to properly support JCR versioning we will have to make the version
store available to all workspaces in oak. though, right now we don't
even support multiple workspaces in oak. this means in a first step
we
On 30.11.12 9:01, Bertrand Delacretaz wrote:
Hi,
On Thu, Nov 29, 2012 at 3:11 PM, Marcel Reutegger mreut...@adobe.com wrote:
...to properly support JCR versioning we will have to make the version
store available to all workspaces in oak. though, right now we don't
even support multiple
hi all,
during the last oak hackathon in basel a couple of people started a
discussion how to implement JCR versioning in oak. I'd like to give
a quick overview what was discussed and how I think we could implement
the various version related operations in oak.
to properly support JCR versioning
On 29.11.2012, at 15:11, Marcel Reutegger mreut...@adobe.com wrote:
- the version store is mounted at the NodeState level. this has the
advantage of being easier to implement, because the API is rather
small. it would also allow us to enforce write protection on the version
store by exposing
