[jira] Updated: (JCR-2106) SystemSessions created for GarbageCollector are not logged out of

[ https://issues.apache.org/jira/browse/JCR-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dettman updated JCR-2106: --- Attachment: JCR-2106-2nd.patch Patch against latest build (on top of previous patch). Stores the sessio

[jira] Reopened: (JCR-2106) SystemSessions created for GarbageCollector are not logged out of

[ https://issues.apache.org/jira/browse/JCR-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dettman reopened JCR-2106: You're welcome... unfortunately the previous patch was not quite right. The GarbageCollector needs to ke

[jira] Resolved: (JCR-2060) JSR 283: Access Nodes and Properties by Array of "NameGlob"

[ https://issues.apache.org/jira/browse/JCR-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Guggisberg resolved JCR-2060. Resolution: Fixed implemented in svn r773588 > JSR 283: Access Nodes and Properties by Array

[jira] Resolved: (JCR-2106) SystemSessions created for GarbageCollector are not logged out of

[ https://issues.apache.org/jira/browse/JCR-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2106. - Resolution: Fixed Committed in revision 773555 (trunk) Thanks a lot for the patch! > SystemSessio

[jira] Updated: (JCR-2106) SystemSessions created for GarbageCollector are not logged out of

[ https://issues.apache.org/jira/browse/JCR-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2106: Issue Type: Improvement (was: Bug) > SystemSessions created for GarbageCollector are not logged out

[jira] Commented: (JCR-1634) In XA transaction session.addLockToken() does not have effect

[ https://issues.apache.org/jira/browse/JCR-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707995#action_12707995 ] Marius Ropotica commented on JCR-1634: -- Great. I didn't test the patch, but as soon as I

[jira] Assigned: (JCR-2106) SystemSessions created for GarbageCollector are not logged out of

[ https://issues.apache.org/jira/browse/JCR-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller reassigned JCR-2106: --- Assignee: Thomas Mueller > SystemSessions created for GarbageCollector are not logged out of >

[jira] Assigned: (JCR-2060) JSR 283: Access Nodes and Properties by Array of "NameGlob"

[ https://issues.apache.org/jira/browse/JCR-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Guggisberg reassigned JCR-2060: -- Assignee: Stefan Guggisberg > JSR 283: Access Nodes and Properties by Array of "NameGlob"

[jira] Resolved: (JCR-2059) JSR 283: Access Property/Node from Session

[ https://issues.apache.org/jira/browse/JCR-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Guggisberg resolved JCR-2059. Resolution: Fixed resolving as fixed. test case coverage is dealt with in issue JCR-2085 >

Re: jdbc2jcr

Hi, On Mon, May 11, 2009 at 11:19 AM, KÖLL Claus wrote: > i have modified a little bit the jdbc2jcr bridge and i want to know how > i should handle this features ... i have also some ideas for it Cool! > should i commit that changes or should we add a jira component > .. what do you think ...

jdbc2jcr

hi (jukka) ... i have modified a little bit the jdbc2jcr bridge and i want to know how i should handle this features ... i have also some ideas for it should i commit that changes or should we add a jira component .. what do you think ... greets claus

RE: Lucene 2.4.1 and jackrabbit-core-1.5.4

Jukka, thanks for your answer! I think we'll give it a try then. Best wishes, Martijn > -Original Message- > From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] > Sent: Monday, May 11, 2009 9:00 AM > To: dev@jackrabbit.apache.org > Subject: Re: Lucene 2.4.1 and jackrabbit-core-1.5.4 > >

[jira] Updated: (JCR-1634) In XA transaction session.addLockToken() does not have effect

[ https://issues.apache.org/jira/browse/JCR-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Köll updated JCR-1634: Attachment: patch2.txt now it works > In XA transaction session.addLockToken() does not have effect > --

[jira] Updated: (JCR-1634) In XA transaction session.addLockToken() does not have effect

[ https://issues.apache.org/jira/browse/JCR-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Köll updated JCR-1634: Attachment: (was: patch2.txt) > In XA transaction session.addLockToken() does not have effect > -

[jira] Resolved: (JCR-1633) When node is created and locked in same transaction, exception is thrown

[ https://issues.apache.org/jira/browse/JCR-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Köll resolved JCR-1633. - Resolution: Fixed Fix Version/s: 1.6.0 resolved in 773483 > When node is created and locked in same

Re: Lucene 2.4.1 and jackrabbit-core-1.5.4

Hi, On Fri, May 8, 2009 at 8:00 AM, Martijn Hendriks wrote: > I've been looking at merging the patch for issue JCR-1855 to > jackrabbit-core-1.5.4 to > get rid of a lucene memory leak, but for me that's not straightforward. I > noticed, > however, that the core compiles and builds (including al