[jira] Resolved: (JCR-601) Delete workspace support

2009-01-12 Thread angela (JIRA)
[ https://issues.apache.org/jira/browse/JCR-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela resolved JCR-601. Resolution: Won't Fix this issue (delete workspace support in jackrabbit API) should from my point of view be resolve

Migrating JCR-RMI to the JCR Commons subproject

2009-01-12 Thread Jukka Zitting
Hi, I started setting up the new JCR Commons subproject by using the JCR-RMI component as the first example. Here are the steps I've taken so far: 1) Create the JCRRMI project in Jira. 2) Migrate all open "jackrabbit-jcr-rmi" issues from JCR to JCRRMI. 3) Create the repos/asf/jackrabbit/commons/j

[jira] Updated: (JCRRMI-4) RMI: Allow custom socket factories

2009-01-12 Thread Jukka Zitting (JIRA)
[ https://issues.apache.org/jira/browse/JCRRMI-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCRRMI-4: --- Description: The current JCR-RMI server classes always use the default RMI socket factory. Provide a me

[jira] Moved: (JCRRMI-3) Session.isLive() and logout() throw exceptions

2009-01-12 Thread Jukka Zitting (JIRA)
[ https://issues.apache.org/jira/browse/JCRRMI-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting moved JCR-1933 to JCRRMI-3: - Component/s: (was: jackrabbit-jcr-rmi) Affects Version/s: (was: 1.

[jira] Moved: (JCRRMI-6) Streamline the JCR-RMI network interfaces

2009-01-12 Thread Jukka Zitting (JIRA)
[ https://issues.apache.org/jira/browse/JCRRMI-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting moved JCR-300 to JCRRMI-6: Component/s: (was: jackrabbit-jcr-rmi) Workflow: no-reopen-closed, patch-av

[jira] Moved: (JCRRMI-2) ClientObservationManager causes null pointer

2009-01-12 Thread Jukka Zitting (JIRA)
[ https://issues.apache.org/jira/browse/JCRRMI-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting moved JCR-1643 to JCRRMI-2: - Component/s: (was: jackrabbit-jcr-rmi) Affects Version/s: (was: rm

[jira] Moved: (JCRRMI-4) RMI: Allow custom socket factories

2009-01-12 Thread Jukka Zitting (JIRA)
[ https://issues.apache.org/jira/browse/JCRRMI-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting moved JCR-781 to JCRRMI-4: Component/s: (was: jackrabbit-jcr-rmi) Description: (was: The current JCR-

[jira] Moved: (JCRRMI-5) Improve the JCR-RMI Value classes

2009-01-12 Thread Jukka Zitting (JIRA)
[ https://issues.apache.org/jira/browse/JCRRMI-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting moved JCR-301 to JCRRMI-5: Component/s: (was: jackrabbit-jcr-rmi) Workflow: no-reopen-closed, patch-av

org.apache.jcr for the JCR Commons subproject

2009-01-12 Thread Jukka Zitting
Hi, I'd like to start using org.apache.jcr as the package root and Maven groupId of the components in the new JCR Commons subproject to clarify the distinction between "Jackrabbit, the content repository" and the generic JCR tools we'll have in JCR Commons. Doing so will require changes to all cl

[jira] Created: (JCRRMI-1) Copy the JCR-RMI component to the new JCR Commons subproject

2009-01-12 Thread Jukka Zitting (JIRA)
Copy the JCR-RMI component to the new JCR Commons subproject Key: JCRRMI-1 URL: https://issues.apache.org/jira/browse/JCRRMI-1 Project: Jackrabbit JCR-RMI Issue Type: Task

[jira] Issue Comment Edited: (JCR-1778) BindableRepositoryFactory doesn't handle repository shutdown

2009-01-12 Thread JIRA
[ https://issues.apache.org/jira/browse/JCR-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663117#action_12663117 ] gjoseph edited comment on JCR-1778 at 1/12/09 2:08 PM: -- Seems to

[jira] Commented: (JCR-1778) BindableRepositoryFactory doesn't handle repository shutdown

2009-01-12 Thread JIRA
[ https://issues.apache.org/jira/browse/JCR-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663117#action_12663117 ] Grégory Joseph commented on JCR-1778: - Seems to as this is (if only by accident) related

[jira] Assigned: (JCRSITE-2) Add articles/tutorials page

2009-01-12 Thread Alexander Klimetschek (JIRA)
[ https://issues.apache.org/jira/browse/JCRSITE-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek reassigned JCRSITE-2: --- Assignee: Alexander Klimetschek > Add articles/tutorials page > --

Re: JCRSITE project created

2009-01-12 Thread Alexander Klimetschek
On Mon, Jan 12, 2009 at 7:25 PM, Jukka Zitting wrote: > On Mon, Jan 12, 2009 at 7:09 PM, Alexander Klimetschek > wrote: >> But it seems I (and probably other committers as well) don't have the >> rights to assign issues - although I can edit, comment, attach files, >> resolve issue etc. > > Shou

Re: JCRSITE project created

2009-01-12 Thread Jukka Zitting
Hi, On Mon, Jan 12, 2009 at 6:40 PM, Jukka Zitting wrote: > I created a new JCRSITE [1] project in Jira for tracking changes to > the Jackrabbit web site, the Jackrabbit parent POM (as discussed for > the JCR Commons subproject), and other resources for which we don't > have a more specific issue

[jira] Updated: (JCRSITE-4) Implementation Architecture Documentation

2009-01-12 Thread Jukka Zitting (JIRA)
[ https://issues.apache.org/jira/browse/JCRSITE-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCRSITE-4: Description: Create Generic Documentation that decribes the Architecture and Operations of Jackrabb

[jira] Moved: (JCRSITE-8) Installation guide

2009-01-12 Thread Jukka Zitting (JIRA)
[ https://issues.apache.org/jira/browse/JCRSITE-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting moved JCR-151 to JCRSITE-8: - Component/s: (was: docs) site Workflow: no-reopen-close

[jira] Updated: (JCRSITE-3) Simple standalone sample apps

2009-01-12 Thread Jukka Zitting (JIRA)
[ https://issues.apache.org/jira/browse/JCRSITE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCRSITE-3: Description: It would be great to have really simple standalone sample apps for the most important

[jira] Moved: (JCRSITE-6) Update / Fix Documentation for CND Notation

2009-01-12 Thread Jukka Zitting (JIRA)
[ https://issues.apache.org/jira/browse/JCRSITE-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting moved JCR-1194 to JCRSITE-6: -- Component/s: (was: docs) site Workflow: no-reopen-clo

[jira] Moved: (JCRSITE-7) Improve Javadoc documentation

2009-01-12 Thread Jukka Zitting (JIRA)
[ https://issues.apache.org/jira/browse/JCRSITE-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting moved JCR-73 to JCRSITE-7: Fix Version/s: (was: none) Component/s: (was: docs)

[jira] Moved: (JCRSITE-5) Update "First Hops" Documentation

2009-01-12 Thread Jukka Zitting (JIRA)
[ https://issues.apache.org/jira/browse/JCRSITE-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting moved JCR-941 to JCRSITE-5: - Fix Version/s: (was: none) Component/s: (was: docs)

[jira] Moved: (JCRSITE-4) Implementation Architecture Documentation

2009-01-12 Thread Jukka Zitting (JIRA)
[ https://issues.apache.org/jira/browse/JCRSITE-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting moved JCR-1 to JCRSITE-4: --- Component/s: (was: docs) site Description: (was: Create Ge

[jira] Moved: (JCRSITE-3) Simple standalone sample apps

2009-01-12 Thread Jukka Zitting (JIRA)
[ https://issues.apache.org/jira/browse/JCRSITE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting moved JCR-1473 to JCRSITE-3: -- Component/s: (was: docs) site Descript

[jira] Resolved: (JCRSITE-1) Create new project-level Jackrabbit parent POM

2009-01-12 Thread Jukka Zitting (JIRA)
[ https://issues.apache.org/jira/browse/JCRSITE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting resolved JCRSITE-1. - Resolution: Fixed I think I have the new parent POM in a pretty good shape now in https://svn.apa

Re: JCRSITE project created

2009-01-12 Thread Jukka Zitting
Hi, On Mon, Jan 12, 2009 at 7:09 PM, Alexander Klimetschek wrote: > But it seems I (and probably other committers as well) don't have the > rights to assign issues - although I can edit, comment, attach files, > resolve issue etc. Should be fixed now. BR, Jukka Zitting

[jira] Commented: (JCR-1933) Session.isLive() and logout() throw exceptions

2009-01-12 Thread Alexander Klimetschek (JIRA)
[ https://issues.apache.org/jira/browse/JCR-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663029#action_12663029 ] Alexander Klimetschek commented on JCR-1933: > - Session.isLive(): return false i

Re: JCRSITE project created

2009-01-12 Thread Alexander Klimetschek
On Mon, Jan 12, 2009 at 6:40 PM, Jukka Zitting wrote: > I created a new JCRSITE [1] project in Jira for tracking changes to > the Jackrabbit web site, the Jackrabbit parent POM (as discussed for > the JCR Commons subproject), and other resources for which we don't > have a more specific issue trac

[jira] Created: (JCRSITE-2) Add articles/tutorials page

2009-01-12 Thread Alexander Klimetschek (JIRA)
Add articles/tutorials page --- Key: JCRSITE-2 URL: https://issues.apache.org/jira/browse/JCRSITE-2 Project: Jackrabbit Site Issue Type: Improvement Components: site Reporter: Alexander Klimetsch

Setting up a new parent POM (Was: [VOTE] Create the JCR Commons subproject)

2009-01-12 Thread Jukka Zitting
Hi, On Wed, Jan 7, 2009 at 8:03 AM, Felix Meschberger wrote: > I think the parent project is truly Jackrabbit global. As such it does > not belong to the Commons subproject. That's a good point, and I agree that we should go that way. I'll be setting up the new parent POM (as described in JCRSIT

[jira] Created: (JCRSITE-1) Create new project-level Jackrabbit parent POM

2009-01-12 Thread Jukka Zitting (JIRA)
Create new project-level Jackrabbit parent POM -- Key: JCRSITE-1 URL: https://issues.apache.org/jira/browse/JCRSITE-1 Project: Jackrabbit Site Issue Type: Task Components: parent

JCRSITE project created

2009-01-12 Thread Jukka Zitting
Hi, I created a new JCRSITE [1] project in Jira for tracking changes to the Jackrabbit web site, the Jackrabbit parent POM (as discussed for the JCR Commons subproject), and other resources for which we don't have a more specific issue tracker. Like the JCRCMIS project, JCRSITE has wiki markup en

[jira] Commented: (JCR-1931) SharedFieldCache$StringIndex memory leak causing OOM's

2009-01-12 Thread Jukka Zitting (JIRA)
[ https://issues.apache.org/jira/browse/JCR-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663010#action_12663010 ] Jukka Zitting commented on JCR-1931: Seems OK to me too. Ard, can you commit this with Ma

[jira] Created: (JCR-1933) Session.isLive() and logout() throw exceptions

2009-01-12 Thread Marcel Reutegger (JIRA)
Session.isLive() and logout() throw exceptions -- Key: JCR-1933 URL: https://issues.apache.org/jira/browse/JCR-1933 Project: Jackrabbit Issue Type: Bug Components: jackrabbit-jcr-rmi

[jira] Commented: (JCR-1823) Repository.login throws IllegalStateException

2009-01-12 Thread JIRA
[ https://issues.apache.org/jira/browse/JCR-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662990#action_12662990 ] Grégory Joseph commented on JCR-1823: - I might be wrong, but I seem to remember this is t

[jira] Commented: (JCR-1664) JNDI Referencable Issues

2009-01-12 Thread Jukka Zitting (JIRA)
[ https://issues.apache.org/jira/browse/JCR-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662986#action_12662986 ] Jukka Zitting commented on JCR-1664: I just noticed that revision 683268 that contained c

[jira] Commented: (JCR-1932) Session.getAttributes( ) call always returns an empty array

2009-01-12 Thread Alexander Klimetschek (JIRA)
[ https://issues.apache.org/jira/browse/JCR-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662964#action_12662964 ] Alexander Klimetschek commented on JCR-1932: Looking at the SessionImpl code, I s

[jira] Commented: (JCR-1931) SharedFieldCache$StringIndex memory leak causing OOM's

2009-01-12 Thread Marcel Reutegger (JIRA)
[ https://issues.apache.org/jira/browse/JCR-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662960#action_12662960 ] Marcel Reutegger commented on JCR-1931: --- Comments: - can you please create a patch tha

Re: [Website] Prominent links to articles

2009-01-12 Thread Jukka Zitting
Hi, On Mon, Jan 12, 2009 at 1:15 PM, Alexander Klimetschek wrote: > WDYT? +1 BR, Jukka Zitting

[Website] Prominent links to articles

2009-01-12 Thread Alexander Klimetschek
Hi all, there are a lot of good both introductionary and detailed articles about JCR and Jackrabbit on the web. We link them on the wiki [1], but this requires to non-obvious clicks from the jackrabbit homepage ("wiki" -> "jcr links") amongst dozens of others. Therefore I would like to create a n

[jira] Commented: (JCR-1892) Unique ID for org.apache.jackrabbit.value.BinaryValue

2009-01-12 Thread Thomas Mueller (JIRA)
[ https://issues.apache.org/jira/browse/JCR-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662918#action_12662918 ] Thomas Mueller commented on JCR-1892: - What about "The identifier is opaque, meaning it

[jira] Updated: (JCR-1932) Session.getAttributes( ) call always returns an empty array

2009-01-12 Thread alessandro cosenza (JIRA)
[ https://issues.apache.org/jira/browse/JCR-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] alessandro cosenza updated JCR-1932: Summary: Session.getAttributes( ) call always returns an empty array (was: bug in JCR API Se

[cmis] api and general structure, client implementation

2009-01-12 Thread David Nuescheler
hi all, i think we are making great progress on the server side of the cmis implementation and it is great to see both the ws and the atompub binding progress so quickly. since i think it should also be a goal of this implementation to make our code as re-uable as possible, it is great that it do