AW: lock problem in xa transaction

should it be possible to create a node and after save to set a non session scoped lock inside one transaction ? As i can see the HierarchyManager does not know the before created node should i open a jira issue ? thanks claus -Ursprüngliche Nachricht- Von: KÖLL Claus [mailto:[EMAIL PRO

[jira] Created: (JCR-1701) InfiniteLoop in bundle binding

InfiniteLoop in bundle binding -- Key: JCR-1701 URL: https://issues.apache.org/jira/browse/JCR-1701 Project: Jackrabbit Issue Type: Bug Affects Versions: 1.5 Reporter: Matej Knopp Prior

[jira] Resolved: (JCR-1700) Deprecate NamespaceListener and AbstractNamespaceResolver

[ https://issues.apache.org/jira/browse/JCR-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting resolved JCR-1700. Resolution: Fixed NamespaceListener and AbstractNamespaceResolver are deprecated and unused as of re

[jira] Created: (JCR-1700) Deprecate NamespaceListener and AbstractNamespaceResolver

Deprecate NamespaceListener and AbstractNamespaceResolver - Key: JCR-1700 URL: https://issues.apache.org/jira/browse/JCR-1700 Project: Jackrabbit Issue Type: Improvement Compo

[jira] Commented: (JCR-1644) make NamespaceContext#getPrefix(java.lang.String) iterative instead of recursive

[ https://issues.apache.org/jira/browse/JCR-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618366#action_12618366 ] Jukka Zitting commented on JCR-1644: The stack overflows on NamespaceContext should reall

[jira] Resolved: (JCR-1699) Do not log warning when coercing value in query is not possible

[ https://issues.apache.org/jira/browse/JCR-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-1699. --- Resolution: Fixed Fix Version/s: 1.5 Fixed in revision: 681059 > Do not log warning whe

[jira] Created: (JCR-1699) Do not log warning when coercing value in query is not possible

Do not log warning when coercing value in query is not possible --- Key: JCR-1699 URL: https://issues.apache.org/jira/browse/JCR-1699 Project: Jackrabbit Issue Type: Improvement

[jira] Resolved: (JCR-1697) Simple Google style query

[ https://issues.apache.org/jira/browse/JCR-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-1697. --- Resolution: Fixed Fix Version/s: 1.5 Added o.a.j.commons.query.GQL in revision: 681049.

[jira] Resolved: (JCR-1698) Remove unnecessary TestAll classes in jcr-commons

[ https://issues.apache.org/jira/browse/JCR-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-1698. --- Resolution: Fixed Fix Version/s: 1.5 Removed TestAll classes in revision: 681036 > Remo

[jira] Created: (JCR-1698) Remove unnecessary TestAll classes in jcr-commons

Remove unnecessary TestAll classes in jcr-commons - Key: JCR-1698 URL: https://issues.apache.org/jira/browse/JCR-1698 Project: Jackrabbit Issue Type: Test Components: jackrabbit-jcr-c

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

[ https://issues.apache.org/jira/browse/JCR-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting resolved JCR-1664. Resolution: Fixed Assignee: Jukka Zitting Patch applied in revision 681031. Resolving as Fixed.

[jira] Created: (JCR-1697) Simple Google style query

Simple Google style query - Key: JCR-1697 URL: https://issues.apache.org/jira/browse/JCR-1697 Project: Jackrabbit Issue Type: New Feature Components: jackrabbit-jcr-commons Reporter: Marcel Reute

[jira] Commented: (JCR-1573) Lucene Query Exception: 'attempt to access a deleted document'

[ https://issues.apache.org/jira/browse/JCR-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618327#action_12618327 ] Marcel Reutegger commented on JCR-1573: --- David, while going though this issue again, I

[jira] Commented: (JCR-1573) Lucene Query Exception: 'attempt to access a deleted document'

[ https://issues.apache.org/jira/browse/JCR-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618308#action_12618308 ] Kurz Wolfgang commented on JCR-1573: Hello everyone, i am having the same problem. The

[jira] Commented: (JCR-1644) make NamespaceContext#getPrefix(java.lang.String) iterative instead of recursive

[ https://issues.apache.org/jira/browse/JCR-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618259#action_12618259 ] fabrizio giustina commented on JCR-1644: I also can confirm it definitively was a Sta

lock problem in xa transaction

if i try a testcase like this ... public void testAddNodeAndLock() throws Exception { UserTransaction utx = new UserTransactionImpl(superuser); // start transaction utx.begin(); // add node and save Node n = testRootNode.addNode(nodeName1, testNodeType); n.addMixin(mixLockable);