Re: javax.jcr.version.VersionException: Unable to select appropariate version

I did a little invesitigation and found out that if I have a child with MIX_VERSIONABLE then it throws these errors when going forward in a restore point. Removing these from children fixes it. But I am baffled why this is. Any help would be appreciated. AmirRaminfar wrote: > > I have read al

Re: javax.jcr.version.VersionException: Unable to select appropariate version

By the way, I am pretty sure it has to do something with froze states. But I don't know what that means. :( AmirRaminfar wrote: > > I have read almost every documentation out there on how to use version > correctly. I am trying to restore to an old version and then back to the > most recent ver

javax.jcr.version.VersionException: Unable to select appropariate version

I have read almost every documentation out there on how to use version correctly. I am trying to restore to an old version and then back to the most recent version. but this seems to break. Here is what I am trying to do in abstract: create node call test checkout test create child node under tes

Build failed in Hudson: Jackrab bit-trunk » Jackrabbit Core #834

See http://hudson.zones.apache.org/hudson/job/Jackrabbit-trunk/org.apache.jackrabbit$jackrabbit-core/834/ -- [INFO] [INFO] Building Jackrabbit Core [INFO]task-segment: [clean, depl

[jira] Updated: (JCR-2307) BLOBFileValue.read(byte[] b, long pos) ignores return value of InputStream.skip

[ https://issues.apache.org/jira/browse/JCR-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2307: Fix Version/s: 2.0.0 > BLOBFileValue.read(byte[] b, long pos) ignores return value of > InputStream.

[jira] Resolved: (JCR-2307) BLOBFileValue.read(byte[] b, long pos) ignores return value of InputStream.skip

[ https://issues.apache.org/jira/browse/JCR-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2307. - Resolution: Fixed > BLOBFileValue.read(byte[] b, long pos) ignores return value of > InputStream.s

Re: [VOTE] Release Apache Jackrabbit 2.0 alpha11

Jukka Zitting wrote: Hi, Here's the candidate for a new Jackrabbit 2.0 alpha release: http://people.apache.org/~jukka/jackrabbit/2.0-alpha11/ See the RELEASE-NOTES.txt file (also included at the end of this message) for details about this release. The release candidate is a jar archive of t

[jira] Created: (JCR-2307) BLOBFileValue.read(byte[] b, long pos) ignores return value of InputStream.skip

BLOBFileValue.read(byte[] b, long pos) ignores return value of InputStream.skip --- Key: JCR-2307 URL: https://issues.apache.org/jira/browse/JCR-2307 Project: Jackrabbit Conte

[VOTE] Release Apache Jackrabbit 2.0 alpha11

Hi, Here's the candidate for a new Jackrabbit 2.0 alpha release: http://people.apache.org/~jukka/jackrabbit/2.0-alpha11/ See the RELEASE-NOTES.txt file (also included at the end of this message) for details about this release. The release candidate is a jar archive of the sources in http

[jira] Commented: (JCR-2299) Bad check for sv:name attribute presence in system view import

[ https://issues.apache.org/jira/browse/JCR-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756059#action_12756059 ] Jukka Zitting commented on JCR-2299: > Restore 1.6.1 fix version (removed by mistake) O

[jira] Updated: (JCR-2299) Bad check for sv:name attribute presence in system view import

[ https://issues.apache.org/jira/browse/JCR-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sébastien Launay updated JCR-2299: -- Fix Version/s: 1.6.1 Restore 1.6.1 fix version (removed by mistake) > Bad check for sv:name attr

[jira] Updated: (JCR-2134) Data Store: enable and fix tests

[ https://issues.apache.org/jira/browse/JCR-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-2134: --- Fix Version/s: 2.0-alpha11 > Data Store: enable and fix tests > > >

[jira] Updated: (JCR-2269) Possible concurrency bug with Workspace.copy()

[ https://issues.apache.org/jira/browse/JCR-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-2269: --- Fix Version/s: 2.0-alpha11 > Possible concurrency bug with Workspace.copy() >

[jira] Updated: (JCR-2300) Does not retain order of child nodes on Orderable nodes when calling Node.update(srcWorkspace)

[ https://issues.apache.org/jira/browse/JCR-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-2300: --- Fix Version/s: (was: 2.0-alpha11) 2.0.0 > Does not retain order of child nodes o

[jira] Commented: (JCR-1878) Use Apache Tika for text extraction

[ https://issues.apache.org/jira/browse/JCR-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756034#action_12756034 ] Jukka Zitting commented on JCR-1878: I have now dropped the jackrabbit-text-extractors co

Build failed in Hudson: Jackrabbit-trunk-tests-java14 #229

See http://hudson.zones.apache.org/hudson/job/Jackrabbit-trunk-tests-java14/229/ -- started Building remotely on minerva.apache.org (Ubuntu) ERROR: svn: timed out waiting for server svn: OPTIONS request failed on '/repos/asf/jackrabbit/trunk/jackrabbit-jcr-

[jira] Updated: (JCR-2275) some legal jcr names cause unneccessary server-roundtrips

[ https://issues.apache.org/jira/browse/JCR-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-2275: --- Resolution: Fixed Fix Version/s: 2.0-alpha11 Assignee: Jukka Zitting Status:

[jira] Resolved: (JCR-2288) o.a.jackrabbit.spi.commons.conversion.NameParser should not assume that namespace URI's are registered

[ https://issues.apache.org/jira/browse/JCR-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting resolved JCR-2288. Resolution: Fixed Fix Version/s: 2.0-alpha11 Assignee: Jukka Zitting Fixed in revisio

Improve indexing performance wrt Aggregates

Hello, I want to avoid recreating a lucene Document when using aggregates over and over. This particularly holds when using aggregates for binary data like a pdf. I think using aggregates also for binary data is a good usecase. But, indexing and extracting a large pdf is cpu intensive, and, this c

[jira] Updated: (JCR-2042) RepositoryFactory implementation for jcr2spi

[ https://issues.apache.org/jira/browse/JCR-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated JCR-2042: --- Fix Version/s: 2.0.0 Affects Version/s: 2.0.0 Status: Patch Available (was: Open

[jira] Updated: (JCR-2042) RepositoryFactory implementation for jcr2spi

[ https://issues.apache.org/jira/browse/JCR-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated JCR-2042: --- Attachment: JCR-2042-poc.patch Here's the patch mentioned in my previous comment > RepositoryFactory i

Re: JSR-283 passes the Final Approval Ballot

On Wed, Sep 16, 2009 at 12:39, sorel wrote: > That's a good news, > > Is there a repository where we can get the JCR 2 dependency and the test > cases classes ? The JSR-283 work happens here: https://jsr-283.dev.java.net/ As Jackrabbit is acting as the reference implementation (RI), the basis o

Re: Security Question Jackrabbit 1.6

On Wed, Sep 16, 2009 at 10:20, KÖLL Claus wrote: >>i wouldn't call extending an interface a backward compatibility issue. > ok thats matter of opinion :-) but if we write in the release-notes something > like > > #Apache Jackrabbit 1.6 is fully compatible with the previous 1.x releases. > #A prev

Re: JSR-283 passes the Final Approval Ballot

That's a good news, Is there a repository where we can get the JCR 2 dependency and the test cases classes ? thanks David Nuescheler a écrit : Dear Jackrabbit Community, I am very pleased to announce that jsr-283 has been approved by the executive committee of the jcp and is bound to become

[jira] Commented: (JCR-2273) Lock.getLockToken() returns null for session scoped lock

[ https://issues.apache.org/jira/browse/JCR-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755969#action_12755969 ] Julian Reschke commented on JCR-2273: - 1) Lock.isLockOwningSession() - right; I forgot ab

Jackrabbit 2.0 press release

Hi, I would like to start preparing an official Apache press release to go with the upcoming Jackrabbit 2.0 release. This will be our biggest release since Jackrabbit 1.0 was released 3.5 years ago [1], and I'd like to get also the press involved in spreading the word. See [2] for a good example

Re: Jackrabbit 2.0 release plan

Hi, As David mentioned, JCR 2.0 is now approved and should become available soon. This means that we are getting closer to being able to release Jackrabbit 2.0. As another step on that way I'm doing another alpha release today. I haven't yet looked in detail at all the open feature issues we have

[jira] Commented: (JCR-2288) o.a.jackrabbit.spi.commons.conversion.NameParser should not assume that namespace URI's are registered

[ https://issues.apache.org/jira/browse/JCR-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755941#action_12755941 ] Stefan Guggisberg commented on JCR-2288: > i consider this to be part of JCR-1564 whi

AW: Security Question Jackrabbit 1.6

hi angela, >i wouldn't call extending an interface a backward compatibility issue. ok thats matter of opinion :-) but if we write in the release-notes something like #Apache Jackrabbit 1.6 is fully compatible with the previous 1.x releases. #A previous Apache Jackrabbit 1.x installation can be u

Re: jackrabbit-rmi version number

Hi, On Wed, Sep 16, 2009 at 10:06 AM, KÖLL Claus wrote: > but should we include the source for this package in future releases ? Not in jackrabbit-core releases, just like we don't include the source of the other dependencies we use. The updated source of the JCR Commons components will be rele

[jira] Commented: (JCR-1991) Create osgi bundles for all jars

[ https://issues.apache.org/jira/browse/JCR-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755930#action_12755930 ] Michael Dürig commented on JCR-1991: Yes I'm aware of that. I'll try to resolve it by imp

AW: jackrabbit-rmi version number

hi jukka, thanks for the info .. but should we include the source for this package in future releases ? greets claus -Ursprüngliche Nachricht- Von: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Gesendet: Mittwoch, 16. September 2009 10:02 An: dev@jackrabbit.apache.org Betreff: Re: jac

[jira] Issue Comment Edited: (JCR-2288) o.a.jackrabbit.spi.commons.conversion.NameParser should not assume that namespace URI's are registered

[ https://issues.apache.org/jira/browse/JCR-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755927#action_12755927 ] angela edited comment on JCR-2288 at 9/16/09 1:05 AM: -- i consider this t

[jira] Commented: (JCR-2288) o.a.jackrabbit.spi.commons.conversion.NameParser should not assume that namespace URI's are registered

[ https://issues.apache.org/jira/browse/JCR-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755927#action_12755927 ] angela commented on JCR-2288: - i consider this part to be part of JCR-1564 which should address t

Re: jackrabbit-rmi version number

Hi, On Wed, Sep 16, 2009 at 9:52 AM, KÖLL Claus wrote: > one question regarding the version number of this package. > in the jackrabbit 1.6 release the jcr-rmi-1.5.jar is integrated in the > standalone edition > but in the source package it isn't. all other packages has been updated to > 1.6 ve

[jira] Commented: (JCR-2291) Issues with compiled permissions of ACL provider

[ https://issues.apache.org/jira/browse/JCR-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755925#action_12755925 ] angela commented on JCR-2291: - > It would probably be a good idea to generate a coherent ACL cach

[jira] Commented: (JCR-2293) PathNotFoundException but item exists

[ https://issues.apache.org/jira/browse/JCR-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755924#action_12755924 ] angela commented on JCR-2293: - summary of a short discussion michael and i had yesterday in the o

jackrabbit-rmi version number

hi all ... one question regarding the version number of this package. in the jackrabbit 1.6 release the jcr-rmi-1.5.jar is integrated in the standalone edition but in the source package it isn't. all other packages has been updated to 1.6 version number. .. sorry not all the jcr-servlet is also

[jira] Commented: (JCR-1991) Create osgi bundles for all jars

[ https://issues.apache.org/jira/browse/JCR-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755923#action_12755923 ] Marcel Reutegger commented on JCR-1991: --- > However, jcr-client has a lot of dependencie

Re: Security Question Jackrabbit 1.6

hi I find now time to migrate our 1.4 Environment to 1.6 :-) and there is one thing i don't know exactly. I thought we are backward compatible to older relaeses but the AccessManager Interface introdces new Methods that i have now to implement. i wouldn't call extending an interface a backw

[jira] Commented: (JCR-2273) Lock.getLockToken() returns null for session scoped lock

[ https://issues.apache.org/jira/browse/JCR-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755913#action_12755913 ] angela commented on JCR-2273: - what about Lock#isLockOwningSession from the javadoc: /** *

[jira] Resolved: (JCR-2273) Lock.getLockToken() returns null for session scoped lock

[ https://issues.apache.org/jira/browse/JCR-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela resolved JCR-2273. - Resolution: Invalid "Lock.getLockToken() returns null for session scoped lock" is according to the specification.