I've been reading this thread with interest - and one thing I wanted
to comment on about keeping full version history, and not cleaning up
any data, this sounds like a good way to allow for anyone to take a
snapshot of the repository at any period of time from it's creation
and get an acc
javax.jcr.NamespaceException: : is not a registered namespace uri
-
Key: JCR-888
URL: https://issues.apache.org/jira/browse/JCR-888
Project: Jackrabbit
Issue Type: Bug
[
https://issues.apache.org/jira/browse/JCR-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved JCR-887.
--
Resolution: Fixed
Fix Version/s: (was: 1.3)
1.4
DateField is now pub
DateField class should be public
Key: JCR-887
URL: https://issues.apache.org/jira/browse/JCR-887
Project: Jackrabbit
Issue Type: Wish
Components: query
Affects Versions: 1.3
Reporter
Hi,
On 4/25/07, Martijn Hendriks <[EMAIL PROTECTED]> wrote:
We have built a small command-line tool for JCR import and export. This
tool can also be used for the described upgrade problem. We are happy to
contribute it to the Apache Jackrabbit project if there's interest in it.
If so, how can we
hi martjin,
that sounds good !
i hope somebody ..jukka ;-) will explain you how you can contribute it to
jackrabbit ..
BR
claus
-Ursprüngliche Nachricht-
Von: Martijn Hendriks [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 25. April 2007 16:56
An: dev@jackrabbit.apache.org
Betreff: RE:
Hi,
We have built a small command-line tool for JCR import and export. This tool
can also be used for the described upgrade problem. We are happy to contribute
it to the Apache Jackrabbit project if there's interest in it. If so, how can
we do this?
Regards,
Martijn Hendriks
creative online
Hi,
On 4/25/07, Alexandru Popescu ☀ <[EMAIL PROTECTED]> wrote:
Yes, it is. But not all content is versionable. Is this proposal only
for versionable content? If so, I apologize as I have missed this
part.
The proposal is for all content, but internally it actually keeps full
change histories o
Hi,
On 4/25/07, Alexandru Popescu ☀ <[EMAIL PROTECTED]> wrote:
On 4/25/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> On 4/25/07, Alexandru Popescu ☀ <[EMAIL PROTECTED]> wrote:
> > I see. Now my next question is: how do you clean behind? If a value
> > becomes unreferenced will you or will you n
[
https://issues.apache.org/jira/browse/JCR-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved JCR-886.
--
Resolution: Fixed
Fixed in revision: 532351.
> Index recovery may fail with IllegalArgumentExcept
Index recovery may fail with IllegalArgumentException
-
Key: JCR-886
URL: https://issues.apache.org/jira/browse/JCR-886
Project: Jackrabbit
Issue Type: Bug
Components: query
A
On 4/25/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
Hi,
On 4/25/07, Alexandru Popescu ☀ <[EMAIL PROTECTED]> wrote:
> I see. Now my next question is: how do you clean behind? If a value
> becomes unreferenced will you or will you not clear it?
It won't be cleared unless the repository gets expl
Hi,
On 4/25/07, Alexandru Popescu ☀ <[EMAIL PROTECTED]> wrote:
I see. Now my next question is: how do you clean behind? If a value
becomes unreferenced will you or will you not clear it?
It won't be cleared unless the repository gets explicitly recreated
using some vacuuming process. I don't t
On 4/25/07, Torgeir Veimo <[EMAIL PROTECTED]> wrote:
On 25 Apr 2007, at 14:18, Alexandru Popescu ☀ wrote:
>
> I see. Now my next question is: how do you clean behind? If a value
> becomes unreferenced will you or will you not clear it?
Isn't the purpose of a versioned repository to keep all ol
On 25 Apr 2007, at 14:18, Alexandru Popescu ☀ wrote:
I see. Now my next question is: how do you clean behind? If a value
becomes unreferenced will you or will you not clear it?
Isn't the purpose of a versioned repository to keep all old content?
--
Torgeir Veimo
[EMAIL PROTECTED]
On 4/25/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
Hi,
On 4/25/07, Alexandru Popescu ☀ <[EMAIL PROTECTED]> wrote:
> Another possible problem with the shared values approach is that in a
> concurrent environment accessing these may become a bottleneck as you
> will almost always need to seriali
Hi,
On 4/25/07, Alexandru Popescu ☀ <[EMAIL PROTECTED]> wrote:
Another possible problem with the shared values approach is that in a
concurrent environment accessing these may become a bottleneck as you
will almost always need to serialize the access. Considering that
reading is now a 2 step op
On 4/25/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
Hi,
On 4/25/07, Alexandru Popescu ☀ <[EMAIL PROTECTED]> wrote:
> On 4/23/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> > My idea is to store each value in a unique and immutable "value
> > record" identified by a "value identifier". Duplicate
The Property externalBLOBs can not be configured with the
BundlePerisitenceManager.
---
Key: JCR-885
URL: https://issues.apache.org/jira/browse/JCR-885
Project: Jackrabbi
Hi,
On 4/25/07, Alexandru Popescu ☀ <[EMAIL PROTECTED]> wrote:
On 4/23/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> My idea is to store each value in a unique and immutable "value
> record" identified by a "value identifier". Duplicate values are only
> stored once in a single value record. Th
On 4/23/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
Hi,
I started prototyping the next generation persistence proposal
discussed before, and would like feedback on an idea on how to store
values in this persistence model.
My idea is to store each value in a unique and immutable "value
record"
Hi,
On 4/23/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
The vote passes with seven binding +1 votes. Since the parallel vote
on the Graffito mailing list also passed, I will now proceed to move
the codebase.
The codebase is now in contrib/jackrabbit-jcr-mapping and I've moved
the relevant ope
Hi,
On 4/25/07, Torgeir Veimo <[EMAIL PROTECTED]> wrote:
Can this one be made accessible on a public URL now that it's part of
jackrabbit?
Sure, check out http://jackrabbit.apache.org/dtd/graffito-jcr-mapping.dtd
We should probably re-brand the component, but let's first get things
settled do
On 4/25/07, Marcel Reutegger <[EMAIL PROTECTED]> wrote:
Alexandru Popescu ☀ wrote:
> Sorry to ask a beginner question but what is rep:excerpt() function
> meant for?
It creates a small XML fragment with text fragments where the query matches are
marked up.
example:
//element(*, nt:resource)[jc
The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit version 1.3. The release is available for download
at:
http://jackrabbit.apache.org/downloads.cgi
Release Notes -- Apache Jackrabbit -- Version 1.3
Introduction
Apache Jackrabbit is a fully
Can this one be made accessible on a public URL now that it's part of
jackrabbit?
--
Torgeir Veimo
[EMAIL PROTECTED]
Updates to multiple workspaces (e.g. in a transaction) fail in DatabaseJournal
--
Key: JCR-884
URL: https://issues.apache.org/jira/browse/JCR-884
Project: Jackrabbit
[
https://issues.apache.org/jira/browse/JCR-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-69 to JCR-883:
---
Fix Version/s: (was: 1.0-a1-dev)
Component/s: (was: JCR-Mapping)
[
https://issues.apache.org/jira/browse/JCR-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-77 to JCR-882:
---
Fix Version/s: (was: 1.0-a1-dev)
Component/s: (was: JCR-Mapping)
[
https://issues.apache.org/jira/browse/JCR-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-123 to JCR-881:
Fix Version/s: (was: 1.0-a1-dev)
Component/s: (was: JCR-Mapping)
[
https://issues.apache.org/jira/browse/JCR-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-128 to JCR-879:
Fix Version/s: (was: ocm-1.0)
Component/s: (was: JCR-Nodemanageme
[
https://issues.apache.org/jira/browse/JCR-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-61 to JCR-880:
---
Component/s: (was: JCR-Mapping)
jcr-mapping
Affects
[
https://issues.apache.org/jira/browse/JCR-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-60 to JCR-878:
---
Component/s: (was: JCR-Mapping)
jcr-mapping
Affects
[
https://issues.apache.org/jira/browse/JCR-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-99 to JCR-876:
---
Component/s: (was: JCR-Mapping)
jcr-mapping
Affects
[
https://issues.apache.org/jira/browse/JCR-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-52 to JCR-873:
---
Fix Version/s: (was: 1.0-a1-dev)
Component/s: (was: JCR-Mapping)
[
https://issues.apache.org/jira/browse/JCR-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-76 to JCR-875:
---
Component/s: (was: JCR-Mapping)
jcr-mapping
Key: JCR-875
[
https://issues.apache.org/jira/browse/JCR-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-63 to JCR-874:
---
Component/s: (was: JCR-Mapping)
jcr-mapping
Key: JCR-874
[
https://issues.apache.org/jira/browse/JCR-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-54 to JCR-877:
---
Fix Version/s: (was: 1.0-a1-dev)
Component/s: (was: JCR-Mapping)
[
https://issues.apache.org/jira/browse/JCR-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-74 to JCR-871:
---
Fix Version/s: (was: 1.0-a1-dev)
Component/s: (was: Documentation)
[
https://issues.apache.org/jira/browse/JCR-872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-45 to JCR-872:
---
Fix Version/s: (was: 1.0-a1-dev)
Component/s: (was: JCR-Mapping)
[
https://issues.apache.org/jira/browse/JCR-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-65 to JCR-869:
---
Component/s: (was: JCR-Mapping)
jcr-mapping
Affects
[
https://issues.apache.org/jira/browse/JCR-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-47 to JCR-870:
---
Fix Version/s: (was: 1.0-a1-dev)
Component/s: (was: JCR-Mapping)
[
https://issues.apache.org/jira/browse/JCR-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-79 to JCR-868:
---
Fix Version/s: (was: 1.0-a1-dev)
Component/s: (was: JCR-Nodemanagem
[
https://issues.apache.org/jira/browse/JCR-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-131 to JCR-866:
Fix Version/s: (was: 1.0-a1-dev)
Component/s: (was: JCR-Mapping)
[
https://issues.apache.org/jira/browse/JCR-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-115 to JCR-867:
Component/s: (was: JCR-Mapping)
jcr-mapping
Key: JCR-8
[
https://issues.apache.org/jira/browse/JCR-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-127 to JCR-865:
Fix Version/s: (was: ocm-1.0)
Component/s: (was: JCR-Mapping)
[
https://issues.apache.org/jira/browse/JCR-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved GRFT-72 to JCR-864:
---
Component/s: (was: JCR-Mapping)
jcr-mapping
Assignee: (wa
[
https://issues.apache.org/jira/browse/JCR-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-863:
--
Fix Version/s: (was: 1.3)
1.4
Affects Version/s: (was: 1.2.2)
Hi,
On 4/25/07, Johan Stuyts <[EMAIL PROTECTED]> wrote:
> > Storing all values as a binary field will prevent access to
> the content
> > using standard database tools. You won't be able to look at
> the values
> > in the database without starting Jackrabbit.
>
> I don't consider that to be a de
> > Storing all values as a binary field will prevent access to
> the content
> > using standard database tools. You won't be able to look at
> the values
> > in the database without starting Jackrabbit.
>
> I don't consider that to be a design goal. The values would most
> naturally be stored d
[
https://issues.apache.org/jira/browse/JCR-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-863:
-
Component/s: (was: core)
query
Fix Version/s: 1.3
Affect
Hi James,
can you please create a jira issue for this change, I will then take care of it
from there.
thank you.
regards
marcel
James Hang wrote:
Is there a reason why the org.apache.jackrabbit.core.query.lucene.DateField
class is not public (even though its methods are public)? All the o
[
https://issues.apache.org/jira/browse/JCR-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491554
]
Marcel Reutegger commented on JCR-778:
--
Does it also happen when you close the session? If not then this supports m
Hi,
On 4/25/07, Johan Stuyts <[EMAIL PROTECTED]> wrote:
> A value record would essentially be an array of bytes as defined in
> Value.getStream(). In other words the integer value 123 and the string
> value "123" would both be stored in the same value record. More
Storing all values as a binary
Alexandru Popescu ☀ wrote:
Sorry to ask a beginner question but what is rep:excerpt() function
meant for?
It creates a small XML fragment with text fragments where the query matches are
marked up.
example:
//element(*, nt:resource)[jcr:contains(., 'peeter')]/rep:excerpt()
on the jcr spec w
> A value record would essentially be an array of bytes as defined in
> Value.getStream(). In other words the integer value 123 and the string
> value "123" would both be stored in the same value record. More
> ...
Storing all values as a binary field will prevent access to the content
using stand
Hi,
On 4/24/07, Christoph Kiehl <[EMAIL PROTECTED]> wrote:
Christoph Kiehl wrote:
> I tried the following:
>
> testWorkspace.clone("default", "/" , "/" , false);
My second try was to just clone one of our root nodes:
testWorkspace.clone("default", "/content" , "/content" , false);
The target
57 matches
Mail list logo
