Hi hsp!
I want to know if is there possible that , in model 3 of deployment, I can have
only one repository that has one workspace per each webapp that is in another
web container.
I can't understand very well your first question. You can have a
repository which several workspaces, each
Jukka Zitting wrote:
Please vote on releasing these packages as Apache Jackrabbit 1.0.
[X] +1 Release the packages are Apache Jackrabbit 1.0
predefined node type tests all fail on a windows box when building
jackrabbit from the source distribution. but I only see this as a minor
issue,
Daglian, Michael (IT) wrote:
Out of curiosity, would the features need to be delayed until JSR-283
solidifies further or could work begin earlier (assuming available
time for you/other contributors of course)?
I think work on query features could basically start right away. even
though the
This described method works fine for me, however how do I get a property of
the rootNode of the history? As far as I can see it starts with the first
revision but not with the original node I saved in the very beginning...
when a new versionable node is created, it also creates the respective
Hi.
I just spent some time starting to get familiar with JCR in general, and
with Jackrabbit and jcr-server in particular. Now that everything is up
and running (built from svn, running in Tomcat 5.0.x, just with all the
default settings), I've started to look into the actual WebDAV server
That is a question I want to do too.
Anyway, following your example, when I want to give access to a node with
id=XXX to an user USER, I must create a new propertie, called XXX into the node
the USER belongs to, for ex:
USER (nodetype my:user (nt:folder))
prop1:value1 (property defined in
On Tue, 2006-04-04 at 10:07 -0300, hsp wrote:
Anyway, following your example, when I want to give access to a node
with id=XXX to an user USER, I must create a new propertie, called XXX
into the node the USER belongs to, for ex:
On Tue, 2006-04-04 at 10:26 +0200, Marcel Reutegger wrote:
Sorry if my question wasn't clear...so,
I would to enable a repository server (running in a especific machine with
configuration for all workspaces needed, one per webapp using the repository)
with a application running like a engine for all different webapp running in
another webcontainner of
Hi Walter and Jackrabbit devs,
Walter Raboch wrote:
Hi all,
we just plan to use JackRabbit in an e-learning project with a few
hundred concurrent users. Therefore I am a little concerned about
scalability.
did you find a solution to the scalability problem?
We're faced with a similar
Sorry if my question is so obvious, is a shame that it is not for me.
The acl you said is like 'access control list' ? How could I implement it? Is
there a ready support in jackrabbit for this? How many information must have in
this key.
I would mind this better, please help me about it. I'm a
hi julian
First step was to run the generic test suite Litmus
(http://www.webdav.org/neon/litmus/), which currently reports a range
of failures,
i let litmus run a couple of times in the past and send
the commented results to the list:
1) initial litmus result.
that post also explains,
Therefore I am a little concerned about scalability.
did you find a solution to the scalability problem?
I don't know if you're aware of it, but there's a project/product called
Magnolia that's based on JackRabbit.
It solved its scalability issue by embedding a repository (actually a
set of 4)
[
http://issues.apache.org/jira/browse/JCR-371?page=comments#action_12373098 ]
Giota Karadimitriou commented on JCR-371:
-
Just to add my experience on this, in case it helps:
This issue occured when while trying to perform concurrent versioning
Query dump failed with deep query tree
--
Key: JCR-386
URL: http://issues.apache.org/jira/browse/JCR-386
Project: Jackrabbit
Type: Bug
Components: query
Versions: 1.0
Environment: Jackrabbit 1.0 RC3
Reporter:
Hi Julian,
Just wanted to chime in that I'm also interested in contributing as best I
can to the JCR WebDAV effort, particularly in regard to the use of WebDAV
with the backend SPI. That is, using the JCR API as a client for remotely
accessing (existing) WebDAV server implementations.
Regards,
On 4/4/06, Julian Reschke [EMAIL PROTECTED] wrote:
Regarding PROPPATCH: understood. However, I really tried hard but
couldn't figure out so far how to reconfigure the system so that custom
properties are allowed? Or does this require a change in the code base?
this is what angela meant when
16 matches
Mail list logo
