[RESULT] [VOTE] Release Apache Jackrabbit 2.0.0

Hi, On Wed, Jan 20, 2010 at 6:59 PM, Jukka Zitting wrote: > Please vote on releasing this package as Apache Jackrabbit 2.0.0. The vote passes as follows: +1 Claus Köll +1 Jukka Zitting +1 Marcel Reutegger +1 Martijn Hendriks +1 Michael Dürig +1 Sébastien Launay +1 Th

[jira] Updated: (JCR-2476) Add profile to enable deployment of jackrabbit-standalone

[ https://issues.apache.org/jira/browse/JCR-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-2476: -- Resolution: Won't Fix Status: Resolved (was: Patch Available) Jukka pointed me to the co

Re: svn commit: r902726 - in /jackrabbit/sandbox/jackrabbit2-bundle/jackrabbit-api: ./ pom.xml src/main/java/org/apache/jackrabbit/api/JackrabbitRepository.java

Hi, On 25.01.2010 15:38, Jukka Zitting wrote: > Hi, > > On Mon, Jan 25, 2010 at 3:24 PM, Felix Meschberger wrote: >> On 25.01.2010 15:02, Jukka Zitting wrote: >>> RepositoryManager interface for which we already solved the >>> "administrator-only" access problem. >> >> Please excuse my ignorance

Re: Jackrabbit web app deployment issue

2010/1/25 Bart van der Schans : > On Mon, Jan 25, 2010 at 12:10 PM,   wrote: > The new Tomcat 6.0.24 release has some support to kill threads when > the application fails to stop them: > http://tomcat.apache.org/tomcat-6.0-doc/changelog.html Too bad it doesn't work with Jackrabbit 2.0, which still

Re: svn commit: r902726 - in /jackrabbit/sandbox/jackrabbit2-bundle/jackrabbit-api: ./ pom.xml src/main/java/org/apache/jackrabbit/api/JackrabbitRepository.java

Hi, On Mon, Jan 25, 2010 at 3:24 PM, Felix Meschberger wrote: > On 25.01.2010 15:02, Jukka Zitting wrote: >> RepositoryManager interface for which we already solved the >> "administrator-only" access problem. > > Please excuse my ignorance: What RepositoryManager interface are you > talking of. T

Re: svn commit: r902726 - in /jackrabbit/sandbox/jackrabbit2-bundle/jackrabbit-api: ./ pom.xml src/main/java/org/apache/jackrabbit/api/JackrabbitRepository.java

Hi, On 25.01.2010 15:02, Jukka Zitting wrote: > Hi, > > On Mon, Jan 25, 2010 at 9:45 AM, wrote: >> +Session loginAdministrative(String workspace) throws LoginException, >> +NoSuchWorkspaceException, RepositoryException; > > I quite dislike this method, as it essentially gives a

Re: svn commit: r902726 - in /jackrabbit/sandbox/jackrabbit2-bundle/jackrabbit-api: ./ pom.xml src/main/java/org/apache/jackrabbit/api/JackrabbitRepository.java

Hi, On 25.01.2010 15:02, Jukka Zitting wrote: > Hi, > > On Mon, Jan 25, 2010 at 9:45 AM, wrote: >> +Session loginAdministrative(String workspace) throws LoginException, >> +NoSuchWorkspaceException, RepositoryException; > > I quite dislike this method, as it essentially gives a

Re: svn commit: r902726 - in /jackrabbit/sandbox/jackrabbit2-bundle/jackrabbit-api: ./ pom.xml src/main/java/org/apache/jackrabbit/api/JackrabbitRepository.java

Hi, On Mon, Jan 25, 2010 at 9:45 AM, wrote: > +    Session loginAdministrative(String workspace) throws LoginException, > +            NoSuchWorkspaceException, RepositoryException; I quite dislike this method, as it essentially gives all clients the ability to access the repository as administ

Re: change proposal DataStore

Hi, > extend the datastore interface > workspace name, node name, property name ... I'm not sure if the workspace / node name / node identifier / property name is always available. One advantage of this addition would be: it could speed up garbage collection. If a binary object "knows" the node

Re: change proposal DataStore

On Mon, Jan 25, 2010 at 11:04, JOSE FELIX HERNANDEZ BARRIO wrote: > i think that if we extend the datastore interface, especially the function : > DataRecord addRecord(InputStream stream) > To add more information, for example: workspace name, node name, property > name ... > it would be possible

RE: Jackrabbit web app deployment issue

Bart Many thanks for this. I'll try both options. Regards George -Original Message- From: Bart van der Schans [mailto:b.vandersch...@onehippo.com] Sent: 25 January 2010 11:15 To: dev Subject: Re: Jackrabbit web app deployment issue On Mon, Jan 25, 2010 at 12:10 PM, wrote: > Hi > >

Re: Jackrabbit web app deployment issue

On Mon, Jan 25, 2010 at 12:10 PM, wrote: > Hi > > We're experiencing an issue with regards to the deployment of the jackrabbit > web app version 1.6.0 to tomcat and jetty servers. > > When the servers are closed down, we notice that the jackrabbit deployment > stiil keeps a process open on port 1

Jackrabbit web app deployment issue

Hi We're experiencing an issue with regards to the deployment of the jackrabbit web app version 1.6.0 to tomcat and jetty servers. When the servers are closed down, we notice that the jackrabbit deployment stiil keeps a process open on port 1099. To circumvent, we have to kill the process and the

[jira] Created: (JCR-2477) Log / trace wrapper: upgrade to JCR API 2.0

Log / trace wrapper: upgrade to JCR API 2.0 --- Key: JCR-2477 URL: https://issues.apache.org/jira/browse/JCR-2477 Project: Jackrabbit Content Repository Issue Type: Improvement Components: sa

Re: change proposal DataStore

i think that if we extend the datastore interface, especially the function : DataRecord *addRecord

Re: change proposal DataStore

Hi, Currently there is only data store per repository. If you need a data store per workspace, then you need one repository per workspace. > - Assign a datastore per workspace (customer) so it's possible to measure > (and limit) storage usage for a given customer This more sounds like an "accoun

Moving repository classloader code to Sling

Hi, first, sorry for the crosspost :) I think we briefly discussed this topic some time ago: the Jackrabbit 1.x versions provide a repository classloader which is not available anymore in 2.0. In Sling we provide a complete scripting framework based on top of the repository and we're using the Ja