[
https://issues.apache.org/jira/browse/JCR-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-2537.
-
Resolution: Fixed
Fix Version/s: 2.0.1
spi2davex: clear uri-lookup after removing node identified with
spi2davex: clear uri-lookup after removing node identified with uniqueID
Key: JCR-2537
URL: https://issues.apache.org/jira/browse/JCR-2537
Project: Jackrabbit Content Repository
[
https://issues.apache.org/jira/browse/JCR-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-2537:
Fix Version/s: (was: 2.0.1)
2.1.0
spi2davex: clear uri-lookup after removing node identified
[
https://issues.apache.org/jira/browse/JCR-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-2532:
Fix Version/s: (was: 2.0.1)
2.1.0
spi2davex: session-scoped lock tokens not included in
[
https://issues.apache.org/jira/browse/JCR-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-2527:
Fix Version/s: (was: 2.0.1)
2.1.0
Fix and simplify CryptedSimpleCredentials
[
https://issues.apache.org/jira/browse/JCR-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Guggisberg updated JCR-2511:
---
Component/s: (was: jackrabbit-core)
jackrabbit-jcr-commons
[
https://issues.apache.org/jira/browse/JCR-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Guggisberg resolved JCR-2511.
Resolution: Fixed
Fix Version/s: 2.1.0
fixed in svn r 918915
Value#getBinary() and
[
https://issues.apache.org/jira/browse/JCR-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12841150#action_12841150
]
angela commented on JCR-2454:
-
TODO:
registration of node types is the only left task.
JSR
spi2dav : impersonation not implemented
---
Key: JCR-2538
URL: https://issues.apache.org/jira/browse/JCR-2538
Project: Jackrabbit Content Repository
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/JCR-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-2539:
Component/s: JCR 2.0
spi2dav: Observation's user data not property handled
[
https://issues.apache.org/jira/browse/JCR-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-2541:
Description:
i didn't look at the details just realized that all EventJournalTest of the TCK
fail in the setup
spi2dav: EventFilters not respected
---
Key: JCR-2542
URL: https://issues.apache.org/jira/browse/JCR-2542
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-spi2dav, JCR
[
https://issues.apache.org/jira/browse/JCR-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-2533:
Component/s: query
spi2dav: Implement RepositoryService#checkQueryStatement
[
https://issues.apache.org/jira/browse/JCR-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-2542:
Component/s: observation
spi2dav: EventFilters not respected
---
[
https://issues.apache.org/jira/browse/JCR-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-2541:
Component/s: observation
spi2dav : EventJournal not implemented
---
[
https://issues.apache.org/jira/browse/JCR-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-2540:
Component/s: observation
spi2dav : move/reorder not properly handled by observation
[
https://issues.apache.org/jira/browse/JCR-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-2539:
Component/s: observation
spi2dav: Observation's user data not property handled
[
https://issues.apache.org/jira/browse/JCR-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-2107.
-
Resolution: Fixed
Fix Version/s: 2.1.0
closing this issue.
as far as i know the new query functionality is
Hi,
It may slow down writes around 50%. I think it should be an optional
feature (some storage backends may not support it at all, and there
should be a way to disable / enable it for those backends that can
support it). I think we should support writing our own transaction log
even when using
[
https://issues.apache.org/jira/browse/JCR-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-2454:
Summary: spi2dav: JSR 283 NodeType Management (was: JSR 283 NodeType
Management)
adjusting summary as it only
spi2dav : list of known issues in the pom.xml
-
Key: JCR-2544
URL: https://issues.apache.org/jira/browse/JCR-2544
Project: Jackrabbit Content Repository
Issue Type: Improvement
Hi,
I think the persistence / storage API should be generic enough to
support at least 3 different implementations efficiently:
- an implementation based on a relational database
- a file based implementation
- in-memory
I think the storage API should support some kind of storage session
On Thu, Mar 4, 2010 at 11:39 AM, Thomas Müller thomas.muel...@day.com wrote:
It may slow down writes around 50%. I think it should be an optional
feature (some storage backends may not support it at all, and there
should be a way to disable / enable it for those backends that can
support it).
On Thu, Mar 4, 2010 at 12:21 PM, Thomas Müller thomas.muel...@day.com wrote:
I think the storage API should support some kind of storage session
(normally one storage session for each JCR session). For a relational
database, such a session could map to a database connection.
I think the
[
https://issues.apache.org/jira/browse/JCR-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-2267:
Resolution: Won't Fix
Fix Version/s: 2.1.0
Status: Resolved (was: Patch Available)
[
https://issues.apache.org/jira/browse/JCR-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12841240#action_12841240
]
angela commented on JCR-2267:
-
the proposed patch supresses the exception and just logs a
[
https://issues.apache.org/jira/browse/JCR-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-2544.
-
Resolution: Fixed
I added a complete list of failing tests both to jcr2dav and spi2dav pom.xml at
Revision:
Justin Edelson wrote:
I'll wait a few days :)
see issue JCR-2544.
with *that* list of known issues i managed to run the
conformance test.
JCR-2037 is still open and i would like the latter to
no only run the TCK tests but also all SPI level tests
(few) and the tests defined in jcr2spi (some).
[
https://issues.apache.org/jira/browse/JCR-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12841404#action_12841404
]
Michael Dürig commented on JCR-2528:
The root cause of this is the move operation: when a
[
https://issues.apache.org/jira/browse/JCR-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig resolved JCR-2528.
Resolution: Fixed
Fix Version/s: 2.1.0
Assignee: Michael Dürig
fixed at revision
[
https://issues.apache.org/jira/browse/JCR-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-2504:
---
Status: Patch Available (was: Open)
see attached indexingConfiguration_classpath.diff
Allow
[
https://issues.apache.org/jira/browse/JCR-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Martinez updated JCR-2525:
--
Attachment: JCR_Deadlock_additionalChanges.txt
The previous patch still caused deadlock. After
[
https://issues.apache.org/jira/browse/JCR-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12841737#action_12841737
]
Marcel Reutegger commented on JCR-2524:
---
hmm, you are right. should have looked more
33 matches
Mail list logo
