:
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 draft
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.
hi jukka
thanks for the compilation.
i would like to discuss the nature of exceptions that will
be thrown from the oak-api/spi module.
Good point.
Here's the full list of RepositoryException subclasses defined in JSR 283:
IMO the following exceptions of the the previously complete list
and jcr-repo-identifier) + wsp-Name + item-Path
kind regards
angela
On 3/22/12 3:40 PM, Angela Schreiber wrote:
hi
On 3/22/12 11:18 AM, Jukka Zitting 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
hi
based on my experience over the past couple of weeks i would like
to suggest that we try to get rid of that naming confusion that we
are currently having with 'repository', 'node' and define some sort
of common vocabulary.
i keep getting private mails the seem to be using the term
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
hi jukka
thanks for the summary
To expand on this a bit, here's more detailed diagram that attempts to
identify key APIs (green boxes) and main implementation components
(violet boxes):
http://people.apache.org/~jukka/2012/oak-components.png
looks basically good
The API and protocol
hi thomas
therefore i would strongly suggest to separate jcr-transient
space from an SPI layer from the very beginning.
Yes, I think we all agree on about the separation.
ok... that wasn't totally clear to me.
I think multiple
packages is good enough separation for now, while it doesn't
501 - 509 of 509 matches
Mail list logo
