[
https://issues.apache.org/jira/browse/JCR-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843973#action_12843973
]
Michael Stämpfli commented on JCR-2450:
---
I created a small package, with which I was
[
https://issues.apache.org/jira/browse/JCR-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stämpfli updated JCR-2450:
--
Attachment: jackrabbit-test.zip
Use mvn package to generate the WAR file to reproduce the
[
https://issues.apache.org/jira/browse/JCR-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-2548.
-
Resolution: Cannot Reproduce
Fix Version/s: 2.1.0
Assignee: angela
could not reproduce this
[
https://issues.apache.org/jira/browse/JCR-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12844007#action_12844007
]
Felix Meschberger commented on JCR-2450:
I just stumbled upon a strange thing in the
Hi,
Forgive me if this has been discussed before (yes, I know I should RTFM
and list archives).
I see the UserManager interface has an autoSave(boolean) method, which
must be called to have the user manager persist any created users and
groups immediately after creation. The setup can also be
Hi,
Consier a UserManager not set to autosave mode. I do:
Group g = userManager.createGroup(groupPrincipal);
g.addMemmber(someUser);
This results in an InvalidItemStateException:
javax.jcr.InvalidItemStateException:
c0a1a731-9fea-34fa-aa78-d224bd58a981 has been modified externally
Hi
another thing striked me looking at the UserManager API: there are 4
create methods:
createGroup(Principal);
createGroup(Principal, String);
createUser(String userID, String password, Principal principal,
String intermediatePath);
createUser(String userID,
[
https://issues.apache.org/jira/browse/JCR-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12844010#action_12844010
]
Robert Sauer commented on JCR-2554:
---
Essentially yes. I had breakpoint on all critical
[
https://issues.apache.org/jira/browse/JCR-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12844010#action_12844010
]
Robert Sauer edited comment on JCR-2554 at 3/11/10 10:53 AM:
-
On Thu, Mar 11, 2010 at 10:51 AM, Felix Meschberger fmesc...@gmail.com wrote:
I assume this is because the addMember method calls Item.save() while
the parent node has not been saved yet.
Is this a known issue worth following up to ?
It could be a bug as javax.jcr. Item.save() is @deprecated.
Felix Meschberger wrote:
Hi
another thing striked me looking at the UserManager API: there are 4
create methods:
createGroup(Principal);
createGroup(Principal, String);
createUser(String userID, String password, Principal principal,
String intermediatePath);
hi
What strikes me is, that to actually persist changes made by the
UserManager, the Session.save() method must be called. IMHO for a proper
level of alignment, the UserManager should probably be extended with
save() and rollback() methods.
i don't think this is required.
JSR 283 defines
[
https://issues.apache.org/jira/browse/JCR-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sascha Theves updated JCR-2433:
---
Priority: Blocker (was: Major)
NPE when copying nodes with Workspace.copy()
hi felix
Consier a UserManager not set to autosave mode. I do:
Group g = userManager.createGroup(groupPrincipal)
g.addMemmber(someUser);
This results in an InvalidItemStateException:
javax.jcr.InvalidItemStateException:
c0a1a731-9fea-34fa-aa78-d224bd58a981 has been modified externally
[
https://issues.apache.org/jira/browse/JCR-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12844028#action_12844028
]
Michael Stämpfli commented on JCR-2450:
---
I saw that too but if you look at the
Hi,
On 11.03.2010 12:14, Angela Schreiber wrote:
hi
What strikes me is, that to actually persist changes made by the
UserManager, the Session.save() method must be called. IMHO for a proper
level of alignment, the UserManager should probably be extended with
save() and rollback() methods.
[
https://issues.apache.org/jira/browse/JCR-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Köll updated JCR-2554:
Attachment: Xid.patch
Can you please test this patch in your environment ?
thanks
Deadlock inside
[
https://issues.apache.org/jira/browse/JCR-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Köll updated JCR-2554:
Status: Patch Available (was: Open)
Deadlock inside XASession on Weblogic
spi2dav(ex): Item.isSame() may fail due to incomplete identifier information
Key: JCR-2560
URL: https://issues.apache.org/jira/browse/JCR-2560
Project: Jackrabbit Content
[
https://issues.apache.org/jira/browse/JCR-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-2560:
Component/s: jackrabbit-spi2dav
jackrabbit-jcr-server
Affects Version/s: 2.0.0
[
https://issues.apache.org/jira/browse/JCR-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12844051#action_12844051
]
Claus Köll commented on JCR-2554:
-
Found one more problem .. i will investigate and let you
[
https://issues.apache.org/jira/browse/JCR-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12844058#action_12844058
]
Robert Sauer commented on JCR-2554:
---
Ok, I was just about to verify but will wait then.
SQL2 query - supplying column selector fails with NPE on getColumnName()
Key: JCR-2561
URL: https://issues.apache.org/jira/browse/JCR-2561
Project: Jackrabbit Content Repository
spi2davex: uri-lookup not cleared after reordering referenceable
same-name-siblings
---
Key: JCR-2562
URL: https://issues.apache.org/jira/browse/JCR-2562
Project:
[
https://issues.apache.org/jira/browse/JCR-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-2562.
-
Resolution: Fixed
spi2davex: uri-lookup not cleared after reordering referenceable
same-name-siblings
Add UserManager.createGroup(String groupID) method
--
Key: JCR-2563
URL: https://issues.apache.org/jira/browse/JCR-2563
Project: Jackrabbit Content Repository
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/JCR-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated JCR-2563:
---
Attachment: JCR-2563.patch
Patch providing the the createGroup(String) method:
*
I created JCR-2563 [1] with a proposed patch adding said
createGroup(String) method.
Anyway opposed to me applying this patch ?
Regards
Felix
[1] https://issues.apache.org/jira/browse/JCR-2563
On 11.03.2010 12:38, Felix Meschberger wrote:
Hi,
On 11.03.2010 12:06, Angela Schreiber wrote:
[
https://issues.apache.org/jira/browse/JCR-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller reassigned JCR-2561:
---
Assignee: Thomas Mueller
SQL2 query - supplying column selector fails with NPE on
SQL2 query: QOMFormatter create incorrect NOT conditions
Key: JCR-2564
URL: https://issues.apache.org/jira/browse/JCR-2564
Project: Jackrabbit Content Repository
Issue Type: Bug
[
https://issues.apache.org/jira/browse/JCR-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Köll updated JCR-2554:
Attachment: Xid_v2.patch
Now at first the Xid's will be checked and then the default thread bound logic
[
https://issues.apache.org/jira/browse/JCR-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller resolved JCR-2564.
-
Resolution: Fixed
Fix Version/s: 2.0.1
SQL2 query: QOMFormatter create incorrect NOT
With Xid_v2 applied It's still hitting the error condition in
DefaultISMLocking:136. Concurent threads are now deadlocking in
DefaultISMLocking:67.
I've attached a screenshot detailing state when the initial error occurs.
-Ursprüngliche Nachricht-
Von: Claus Köll (JIRA)
[
https://issues.apache.org/jira/browse/JCR-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12844109#action_12844109
]
Robert Sauer commented on JCR-2554:
---
With Xid_v2 applied It's still hitting the error
[
https://issues.apache.org/jira/browse/JCR-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Sauer updated JCR-2554:
--
Attachment: Xid_v2 + SynchronizedRef for markedXid.jpg
Xid_v2 + SynchronizedRef for markedXid. Still the
[
https://issues.apache.org/jira/browse/JCR-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-2099:
Component/s: jackrabbit-spi2jcr
jackrabbit-spi2dav
jackrabbit-spi
spi2dav: too many warnings related to change polling (NPE and similar)
--
Key: JCR-2566
URL: https://issues.apache.org/jira/browse/JCR-2566
Project: Jackrabbit Content Repository
[
https://issues.apache.org/jira/browse/JCR-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-2536.
-
Resolution: Fixed
Fix Version/s: 2.1.0
Assignee: angela
spi2davex: InvalidItemStateException not
[
https://issues.apache.org/jira/browse/JCR-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-2565.
-
Resolution: Fixed
Fix Version/s: 2.1.0
Assignee: angela
changed overwrite header to F and adjusted
39 matches
Mail list logo
