[JBoss JIRA] Created: (DNA-505) Svn Repository Source with NPE and other issues while opening connection through Jcr
8:04 a.m.
Svn Repository Source with NPE and other issues while opening connection through Jcr
------------------------------------------------------------------------------------
Key: DNA-505
URL: https://jira.jboss.org/jira/browse/DNA-505
Project: DNA
Issue Type: Bug
Components: Connectors
Affects Versions: 0.6
Environment: Mac OS X 10.5 - Jvm 1.5 - Maven 2
Reporter: Luiz Fernando Teston
Durring a test run to read data from some svn repository using Jcr api from DNA, it throws
NullPointerException when trying to read jcr:content for nodes of type folder. This NPEs
was really easy to solve. So, I created a patch for this. After this patch, when running
the same unit test, it throws a repository source exception saying
"svnRepositorySource does not allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java""
workspace".
The stack trace is here also:
org.jboss.dna.graph.connector.RepositorySourceException: svnRepositorySource does not
allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.checkThePath(SVNRepositoryRequestProcessor.java:1000)
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:151)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:641)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:239)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
at
org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:176)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:314)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:06 a.m.
New subject: [JBoss JIRA] Updated: (DNA-505) Svn Repository Source with NPE and other issues while opening connection through Jcr
[
https://jira.jboss.org/jira/browse/DNA-505?page=com.atlassian.jira.plugin...
]
Luiz Fernando Teston updated DNA-505:
-------------------------------------
Attachment: 0001-fixing-a-few-null-pointer-exeptions.patch
Patch for fixing the NPEs on SvnRepositorySource. Sorry about the eclipse files included
on patch :-)
Svn Repository Source with NPE and other issues while opening
connection through Jcr
------------------------------------------------------------------------------------
Key: DNA-505
URL: https://jira.jboss.org/jira/browse/DNA-505
Project: DNA
Issue Type: Bug
Components: Connectors
Affects Versions: 0.6
Environment: Mac OS X 10.5 - Jvm 1.5 - Maven 2
Reporter: Luiz Fernando Teston
Attachments: 0001-fixing-a-few-null-pointer-exeptions.patch
Durring a test run to read data from some svn repository using Jcr api from DNA, it
throws NullPointerException when trying to read jcr:content for nodes of type folder. This
NPEs was really easy to solve. So, I created a patch for this. After this patch, when
running the same unit test, it throws a repository source exception saying
"svnRepositorySource does not allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java""
workspace".
The stack trace is here also:
org.jboss.dna.graph.connector.RepositorySourceException: svnRepositorySource does not
allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.checkThePath(SVNRepositoryRequestProcessor.java:1000)
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:151)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:641)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:239)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
at
org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:176)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:314)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:08 a.m.
New subject: [JBoss JIRA] Updated: (DNA-505) Svn Repository Source with NPE and other issues while opening connection through Jcr
[
https://jira.jboss.org/jira/browse/DNA-505?page=com.atlassian.jira.plugin...
]
Luiz Fernando Teston updated DNA-505:
-------------------------------------
Attachment: DnaSvnUsingJcrWithProgramaticConfigurationTest.java
The unit test to test connection on svn using jcr api
Svn Repository Source with NPE and other issues while opening
connection through Jcr
------------------------------------------------------------------------------------
Key: DNA-505
URL: https://jira.jboss.org/jira/browse/DNA-505
Project: DNA
Issue Type: Bug
Components: Connectors
Affects Versions: 0.6
Environment: Mac OS X 10.5 - Jvm 1.5 - Maven 2
Reporter: Luiz Fernando Teston
Attachments: 0001-fixing-a-few-null-pointer-exeptions.patch,
DnaSvnUsingJcrWithProgramaticConfigurationTest.java
Durring a test run to read data from some svn repository using Jcr api from DNA, it
throws NullPointerException when trying to read jcr:content for nodes of type folder. This
NPEs was really easy to solve. So, I created a patch for this. After this patch, when
running the same unit test, it throws a repository source exception saying
"svnRepositorySource does not allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java""
workspace".
The stack trace is here also:
org.jboss.dna.graph.connector.RepositorySourceException: svnRepositorySource does not
allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.checkThePath(SVNRepositoryRequestProcessor.java:1000)
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:151)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:641)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:239)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
at
org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:176)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:314)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:10 a.m.
New subject: [JBoss JIRA] Commented: (DNA-505) Svn Repository Source with NPE and other issues while opening connection through Jcr
[
https://jira.jboss.org/jira/browse/DNA-505?page=com.atlassian.jira.plugin...
]
Luiz Fernando Teston commented on DNA-505:
------------------------------------------
I believe by solving the issue DNA-240 it issue should be solved also.
Svn Repository Source with NPE and other issues while opening
connection through Jcr
------------------------------------------------------------------------------------
Key: DNA-505
URL: https://jira.jboss.org/jira/browse/DNA-505
Project: DNA
Issue Type: Bug
Components: Connectors
Affects Versions: 0.6
Environment: Mac OS X 10.5 - Jvm 1.5 - Maven 2
Reporter: Luiz Fernando Teston
Attachments: 0001-fixing-a-few-null-pointer-exeptions.patch,
DnaSvnUsingJcrWithProgramaticConfigurationTest.java
Durring a test run to read data from some svn repository using Jcr api from DNA, it
throws NullPointerException when trying to read jcr:content for nodes of type folder. This
NPEs was really easy to solve. So, I created a patch for this. After this patch, when
running the same unit test, it throws a repository source exception saying
"svnRepositorySource does not allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java""
workspace".
The stack trace is here also:
org.jboss.dna.graph.connector.RepositorySourceException: svnRepositorySource does not
allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.checkThePath(SVNRepositoryRequestProcessor.java:1000)
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:151)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:641)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:239)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
at
org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:176)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:314)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:18 a.m.
New subject: [JBoss JIRA] Updated: (DNA-505) Svn Repository Source with NPE and other issues while opening connection through Jcr
[
https://jira.jboss.org/jira/browse/DNA-505?page=com.atlassian.jira.plugin...
]
Randall Hauch updated DNA-505:
------------------------------
Fix Version/s: 0.6
Targeting to fix in 0.6.
Svn Repository Source with NPE and other issues while opening
connection through Jcr
------------------------------------------------------------------------------------
Key: DNA-505
URL: https://jira.jboss.org/jira/browse/DNA-505
Project: DNA
Issue Type: Bug
Components: Connectors
Affects Versions: 0.6
Environment: Mac OS X 10.5 - Jvm 1.5 - Maven 2
Reporter: Luiz Fernando Teston
Fix For: 0.6
Attachments: 0001-fixing-a-few-null-pointer-exeptions.patch,
DnaSvnUsingJcrWithProgramaticConfigurationTest.java
Durring a test run to read data from some svn repository using Jcr api from DNA, it
throws NullPointerException when trying to read jcr:content for nodes of type folder. This
NPEs was really easy to solve. So, I created a patch for this. After this patch, when
running the same unit test, it throws a repository source exception saying
"svnRepositorySource does not allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java""
workspace".
The stack trace is here also:
org.jboss.dna.graph.connector.RepositorySourceException: svnRepositorySource does not
allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.checkThePath(SVNRepositoryRequestProcessor.java:1000)
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:151)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:641)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:239)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
at
org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:176)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:314)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:44 p.m.
New subject: [JBoss JIRA] Commented: (DNA-505) Svn Repository Source with NPE and other issues while opening connection through Jcr
[
https://jira.jboss.org/jira/browse/DNA-505?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-505:
-----------------------------------
One of the NPE issues (DNA-505) was more easily fixed by returning an empty collection;
the other was fixed as prescribed in the patch (though there was another situation that
required a similar change). A test case was added to the 'dna-connector-svn'
project to test using the DNA SVN repository, and this made apparent several other issues.
First, the children for a directory were being computed incorrectly; all of the child
directories were fine, but the locations of the nt:file nodes were being skipped and
instead the path to the nt:file's jcr:content child node were being returned. Second,
much of the JCR implementation relies upon ReadNodeRequest instead of the
ReadAllPropertiesRequest and ReadAllChildrenRequest. Although the default implementation
for ReadNodeRequest uses the other two and is technically correct, it can be quite
inefficient, and this was definitely true for the SVN connector. Therefore, the request
processor code was refactored to have a single method compute the children and/or the
properties for a node. This not only dramatically reduced the class size, but it
dramatically reduced the amount of duplicated code, and it appears to have slightly
improved performance (though I think the SVNKit is still the bottleneck).
Finally, for DNA-240, a new integration test was added to the
'dna-integration-test' project that very minimally tests using JCR on top of the
SVN connector. This may need to be rounded out in the future, but ideally we wouldn't
be hitting a remote SVN repository (simply because of the latency issue).
Svn Repository Source with NPE and other issues while opening
connection through Jcr
------------------------------------------------------------------------------------
Key: DNA-505
URL: https://jira.jboss.org/jira/browse/DNA-505
Project: DNA
Issue Type: Bug
Components: Connectors
Affects Versions: 0.6
Environment: Mac OS X 10.5 - Jvm 1.5 - Maven 2
Reporter: Luiz Fernando Teston
Fix For: 0.6
Attachments: 0001-fixing-a-few-null-pointer-exeptions.patch,
DnaSvnUsingJcrWithProgramaticConfigurationTest.java
Durring a test run to read data from some svn repository using Jcr api from DNA, it
throws NullPointerException when trying to read jcr:content for nodes of type folder. This
NPEs was really easy to solve. So, I created a patch for this. After this patch, when
running the same unit test, it throws a repository source exception saying
"svnRepositorySource does not allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java""
workspace".
The stack trace is here also:
org.jboss.dna.graph.connector.RepositorySourceException: svnRepositorySource does not
allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.checkThePath(SVNRepositoryRequestProcessor.java:1000)
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:151)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:641)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:239)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
at
org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:176)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:314)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:44 p.m.
New subject: [JBoss JIRA] Assigned: (DNA-505) Svn Repository Source with NPE and other issues while opening connection through Jcr
[
https://jira.jboss.org/jira/browse/DNA-505?page=com.atlassian.jira.plugin...
]
Randall Hauch reassigned DNA-505:
---------------------------------
Assignee: Randall Hauch
Svn Repository Source with NPE and other issues while opening
connection through Jcr
------------------------------------------------------------------------------------
Key: DNA-505
URL: https://jira.jboss.org/jira/browse/DNA-505
Project: DNA
Issue Type: Bug
Components: Connectors
Affects Versions: 0.6
Environment: Mac OS X 10.5 - Jvm 1.5 - Maven 2
Reporter: Luiz Fernando Teston
Assignee: Randall Hauch
Fix For: 0.6
Attachments: 0001-fixing-a-few-null-pointer-exeptions.patch,
DnaSvnUsingJcrWithProgramaticConfigurationTest.java
Durring a test run to read data from some svn repository using Jcr api from DNA, it
throws NullPointerException when trying to read jcr:content for nodes of type folder. This
NPEs was really easy to solve. So, I created a patch for this. After this patch, when
running the same unit test, it throws a repository source exception saying
"svnRepositorySource does not allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java""
workspace".
The stack trace is here also:
org.jboss.dna.graph.connector.RepositorySourceException: svnRepositorySource does not
allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.checkThePath(SVNRepositoryRequestProcessor.java:1000)
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:151)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:641)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:239)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
at
org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:176)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:314)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:46 p.m.
New subject: [JBoss JIRA] Commented: (DNA-505) Svn Repository Source with NPE and other issues while opening connection through Jcr
[
https://jira.jboss.org/jira/browse/DNA-505?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-505:
-----------------------------------
Feu, could you verify that this fix has indeed corrected your issues? If so, can you
please reply here, and I will mark as resolved.
Svn Repository Source with NPE and other issues while opening
connection through Jcr
------------------------------------------------------------------------------------
Key: DNA-505
URL: https://jira.jboss.org/jira/browse/DNA-505
Project: DNA
Issue Type: Bug
Components: Connectors
Affects Versions: 0.6
Environment: Mac OS X 10.5 - Jvm 1.5 - Maven 2
Reporter: Luiz Fernando Teston
Assignee: Randall Hauch
Fix For: 0.6
Attachments: 0001-fixing-a-few-null-pointer-exeptions.patch,
DnaSvnUsingJcrWithProgramaticConfigurationTest.java
Durring a test run to read data from some svn repository using Jcr api from DNA, it
throws NullPointerException when trying to read jcr:content for nodes of type folder. This
NPEs was really easy to solve. So, I created a patch for this. After this patch, when
running the same unit test, it throws a repository source exception saying
"svnRepositorySource does not allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java""
workspace".
The stack trace is here also:
org.jboss.dna.graph.connector.RepositorySourceException: svnRepositorySource does not
allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.checkThePath(SVNRepositoryRequestProcessor.java:1000)
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:151)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:641)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:239)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
at
org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:176)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:314)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:02 a.m.
New subject: [JBoss JIRA] Work started: (DNA-505) Svn Repository Source with NPE and other issues while opening connection through Jcr
[
https://jira.jboss.org/jira/browse/DNA-505?page=com.atlassian.jira.plugin...
]
Work on DNA-505 started by Randall Hauch.
Svn Repository Source with NPE and other issues while opening
connection through Jcr
------------------------------------------------------------------------------------
Key: DNA-505
URL: https://jira.jboss.org/jira/browse/DNA-505
Project: DNA
Issue Type: Bug
Components: Connectors
Affects Versions: 0.6
Environment: Mac OS X 10.5 - Jvm 1.5 - Maven 2
Reporter: Luiz Fernando Teston
Assignee: Randall Hauch
Fix For: 0.6
Attachments: 0001-fixing-a-few-null-pointer-exeptions.patch,
DnaSvnUsingJcrWithProgramaticConfigurationTest.java
Durring a test run to read data from some svn repository using Jcr api from DNA, it
throws NullPointerException when trying to read jcr:content for nodes of type folder. This
NPEs was really easy to solve. So, I created a patch for this. After this patch, when
running the same unit test, it throws a repository source exception saying
"svnRepositorySource does not allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java""
workspace".
The stack trace is here also:
org.jboss.dna.graph.connector.RepositorySourceException: svnRepositorySource does not
allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.checkThePath(SVNRepositoryRequestProcessor.java:1000)
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:151)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:641)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:239)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
at
org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:176)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:314)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:42 a.m.
New subject: [JBoss JIRA] Commented: (DNA-505) Svn Repository Source with NPE and other issues while opening connection through Jcr
[
https://jira.jboss.org/jira/browse/DNA-505?page=com.atlassian.jira.plugin...
]
Luiz Fernando Teston commented on DNA-505:
------------------------------------------
Randall, my test worked ok. I'll run some stress tests to read the files contents
right now and I let you know if it worked ok or not.
But I found a simple NPE inside a toString method. When iterating some children nodes from
the root node and calling toString on every node during the iteration I got this NPE:
java.lang.NullPointerException
at org.jboss.dna.jcr.AbstractJcrNode.toString(AbstractJcrNode.java:1693)
at java.lang.String.valueOf(String.java:2615)
at java.io.PrintStream.print(PrintStream.java:616)
at java.io.PrintStream.println(PrintStream.java:753)
It seems to be simple to solve.
Svn Repository Source with NPE and other issues while opening
connection through Jcr
------------------------------------------------------------------------------------
Key: DNA-505
URL: https://jira.jboss.org/jira/browse/DNA-505
Project: DNA
Issue Type: Bug
Components: Connectors
Affects Versions: 0.6
Environment: Mac OS X 10.5 - Jvm 1.5 - Maven 2
Reporter: Luiz Fernando Teston
Assignee: Randall Hauch
Fix For: 0.6
Attachments: 0001-fixing-a-few-null-pointer-exeptions.patch,
DnaSvnUsingJcrWithProgramaticConfigurationTest.java
Durring a test run to read data from some svn repository using Jcr api from DNA, it
throws NullPointerException when trying to read jcr:content for nodes of type folder. This
NPEs was really easy to solve. So, I created a patch for this. After this patch, when
running the same unit test, it throws a repository source exception saying
"svnRepositorySource does not allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java""
workspace".
The stack trace is here also:
org.jboss.dna.graph.connector.RepositorySourceException: svnRepositorySource does not
allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.checkThePath(SVNRepositoryRequestProcessor.java:1000)
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:151)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:641)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:239)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
at
org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:176)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:314)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:56 a.m.
New subject: [JBoss JIRA] Commented: (DNA-505) Svn Repository Source with NPE and other issues while opening connection through Jcr
[
https://jira.jboss.org/jira/browse/DNA-505?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-505:
-----------------------------------
Thanks, Feu. I wasn't able to reproduce, but I changed AbstractJcrNode.toString() to
better handle this situation if it should arise. However, it shouldn't really be
happening in the first place, so I've made a few other changes to try and further
prevent this NPE.
First, the PropertyIterator should never expose a null Property, so the code that is
creating this (and the underlying collection of Property objects) was changed to never add
a null reference to the collection.
Second, the SVN connector had one case where it *might* add a null property object to the
resulting nodes, so the code was changed to handle this case.
Svn Repository Source with NPE and other issues while opening
connection through Jcr
------------------------------------------------------------------------------------
Key: DNA-505
URL: https://jira.jboss.org/jira/browse/DNA-505
Project: DNA
Issue Type: Bug
Components: Connectors
Affects Versions: 0.6
Environment: Mac OS X 10.5 - Jvm 1.5 - Maven 2
Reporter: Luiz Fernando Teston
Assignee: Randall Hauch
Fix For: 0.6
Attachments: 0001-fixing-a-few-null-pointer-exeptions.patch,
DnaSvnUsingJcrWithProgramaticConfigurationTest.java
Durring a test run to read data from some svn repository using Jcr api from DNA, it
throws NullPointerException when trying to read jcr:content for nodes of type folder. This
NPEs was really easy to solve. So, I created a patch for this. After this patch, when
running the same unit test, it throws a repository source exception saying
"svnRepositorySource does not allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java""
workspace".
The stack trace is here also:
org.jboss.dna.graph.connector.RepositorySourceException: svnRepositorySource does not
allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.checkThePath(SVNRepositoryRequestProcessor.java:1000)
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:151)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:641)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:239)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
at
org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:176)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:314)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:56 a.m.
New subject: [JBoss JIRA] Commented: (DNA-505) Svn Repository Source with NPE and other issues while opening connection through Jcr
[
https://jira.jboss.org/jira/browse/DNA-505?page=com.atlassian.jira.plugin...
]
Luiz Fernando Teston commented on DNA-505:
------------------------------------------
Randall, I did some stress tests on Svn connector. The stress tests are pretty the same as
the commited test. The only difference i in this stress test I have a visitor to get the
file content for all valid files inside the jcr repository. I did the same test on File
system connector and it worked well.
So, during the visiting I got this NPE:
Caused by: java.lang.NullPointerException
at org.jboss.dna.jcr.SessionCache.createPropertyInfo(SessionCache.java:2058)
at org.jboss.dna.jcr.SessionCache$JcrNodeOperations.materialize(SessionCache.java:2282)
at org.jboss.dna.graph.session.GraphSession$Node.load(GraphSession.java:1418)
at org.jboss.dna.graph.session.GraphSession$Node.getPayload(GraphSession.java:2624)
at org.jboss.dna.jcr.AbstractJcrNode.getNodes(AbstractJcrNode.java:645)
at
org.openspotlight.federation.data.util.JcrNodeVisitor$VisitorSupport.fillChildren(JcrNodeVisitor.java:158)
at
org.openspotlight.federation.data.util.JcrNodeVisitor$VisitorSupport.fillQueue(JcrNodeVisitor.java:196)
at org.openspotlight.federation.data.util.JcrNodeVisitor.visit(JcrNodeVisitor.java:294)
... 28 more
The line who fires this NPE is a simple Jcr iterator like: final NodeIterator nodeIterator
= n.getNodes();
If you like I can prepare a new test to put on this issue.
Svn Repository Source with NPE and other issues while opening
connection through Jcr
------------------------------------------------------------------------------------
Key: DNA-505
URL: https://jira.jboss.org/jira/browse/DNA-505
Project: DNA
Issue Type: Bug
Components: Connectors
Affects Versions: 0.6
Environment: Mac OS X 10.5 - Jvm 1.5 - Maven 2
Reporter: Luiz Fernando Teston
Assignee: Randall Hauch
Fix For: 0.6
Attachments: 0001-fixing-a-few-null-pointer-exeptions.patch,
DnaSvnUsingJcrWithProgramaticConfigurationTest.java
Durring a test run to read data from some svn repository using Jcr api from DNA, it
throws NullPointerException when trying to read jcr:content for nodes of type folder. This
NPEs was really easy to solve. So, I created a patch for this. After this patch, when
running the same unit test, it throws a repository source exception saying
"svnRepositorySource does not allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java""
workspace".
The stack trace is here also:
org.jboss.dna.graph.connector.RepositorySourceException: svnRepositorySource does not
allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.checkThePath(SVNRepositoryRequestProcessor.java:1000)
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:151)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:641)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:239)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
at
org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:176)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:314)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:20 p.m.
New subject: [JBoss JIRA] Commented: (DNA-505) Svn Repository Source with NPE and other issues while opening connection through Jcr
[
https://jira.jboss.org/jira/browse/DNA-505?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-505:
-----------------------------------
Ah, I believe I know what the problem is. "nt:resource" (the node type used for
the "jcr:data" child node under each "nt:file" object) is required by
the JCR specification to have "mix:referenceable", but the SVN connector is
likely not including a jcr:uuid property in the list. I'll modify my test case to see
if this is the case.
Svn Repository Source with NPE and other issues while opening
connection through Jcr
------------------------------------------------------------------------------------
Key: DNA-505
URL: https://jira.jboss.org/jira/browse/DNA-505
Project: DNA
Issue Type: Bug
Components: Connectors
Affects Versions: 0.6
Environment: Mac OS X 10.5 - Jvm 1.5 - Maven 2
Reporter: Luiz Fernando Teston
Assignee: Randall Hauch
Fix For: 0.6
Attachments: 0001-fixing-a-few-null-pointer-exeptions.patch,
DnaSvnUsingJcrWithProgramaticConfigurationTest.java
Durring a test run to read data from some svn repository using Jcr api from DNA, it
throws NullPointerException when trying to read jcr:content for nodes of type folder. This
NPEs was really easy to solve. So, I created a patch for this. After this patch, when
running the same unit test, it throws a repository source exception saying
"svnRepositorySource does not allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java""
workspace".
The stack trace is here also:
org.jboss.dna.graph.connector.RepositorySourceException: svnRepositorySource does not
allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.checkThePath(SVNRepositoryRequestProcessor.java:1000)
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:151)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:641)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:239)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
at
org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:176)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:314)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:56 p.m.
New subject: [JBoss JIRA] Commented: (DNA-505) Svn Repository Source with NPE and other issues while opening connection through Jcr
[
https://jira.jboss.org/jira/browse/DNA-505?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-505:
-----------------------------------
Yes, that was indeed the problem (though it's not the 'jcr:data' child node,
it's 'jcr:content' - oops). And I was able to reproduce this in the
integration test.
There really isn't a durable UUID available for each file in SVN (there is a single
UUID for each repository, though). And so the SVN connector does not return a
'jcr:uuid' property for the 'jcr:content' node, and this fouls up the
SessionCache implementation. However, while 'nt:file' and 'nt:folder' are
not referenceable, 'nt:resource' is. But lucky for us that the JCR spec does not
require that the 'jcr:content' node has a type of 'nt:resource'; it merely
says:
"A common approach is to make the jcr:content a node of type
nt:resource." (Section 6.7.22.6 of the 1.0.1 version of the JCR specification, page
160.)
So, a solution is to do the same thing we did in the file system connector: use a
'dna:resource' node type that is identical to 'nt:resource' except that it
does not extend 'mix:referenceable'. This appears to have fixed the problem.
Svn Repository Source with NPE and other issues while opening
connection through Jcr
------------------------------------------------------------------------------------
Key: DNA-505
URL: https://jira.jboss.org/jira/browse/DNA-505
Project: DNA
Issue Type: Bug
Components: Connectors
Affects Versions: 0.6
Environment: Mac OS X 10.5 - Jvm 1.5 - Maven 2
Reporter: Luiz Fernando Teston
Assignee: Randall Hauch
Fix For: 0.6
Attachments: 0001-fixing-a-few-null-pointer-exeptions.patch,
DnaSvnUsingJcrWithProgramaticConfigurationTest.java
Durring a test run to read data from some svn repository using Jcr api from DNA, it
throws NullPointerException when trying to read jcr:content for nodes of type folder. This
NPEs was really easy to solve. So, I created a patch for this. After this patch, when
running the same unit test, it throws a repository source exception saying
"svnRepositorySource does not allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java""
workspace".
The stack trace is here also:
org.jboss.dna.graph.connector.RepositorySourceException: svnRepositorySource does not
allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.checkThePath(SVNRepositoryRequestProcessor.java:1000)
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:151)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:641)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:239)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
at
org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:176)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:314)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:58 p.m.
New subject: [JBoss JIRA] Commented: (DNA-505) Svn Repository Source with NPE and other issues while opening connection through Jcr
[
https://jira.jboss.org/jira/browse/DNA-505?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-505:
-----------------------------------
Feu, would you mind getting the latest from trunk (revision 1193 or later) and trying out
the SVN connector? Please let me know how it goes.
Svn Repository Source with NPE and other issues while opening
connection through Jcr
------------------------------------------------------------------------------------
Key: DNA-505
URL: https://jira.jboss.org/jira/browse/DNA-505
Project: DNA
Issue Type: Bug
Components: Connectors
Affects Versions: 0.6
Environment: Mac OS X 10.5 - Jvm 1.5 - Maven 2
Reporter: Luiz Fernando Teston
Assignee: Randall Hauch
Fix For: 0.6
Attachments: 0001-fixing-a-few-null-pointer-exeptions.patch,
DnaSvnUsingJcrWithProgramaticConfigurationTest.java
Durring a test run to read data from some svn repository using Jcr api from DNA, it
throws NullPointerException when trying to read jcr:content for nodes of type folder. This
NPEs was really easy to solve. So, I created a patch for this. After this patch, when
running the same unit test, it throws a repository source exception saying
"svnRepositorySource does not allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java""
workspace".
The stack trace is here also:
org.jboss.dna.graph.connector.RepositorySourceException: svnRepositorySource does not
allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.checkThePath(SVNRepositoryRequestProcessor.java:1000)
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:151)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:641)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:239)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
at
org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:176)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:314)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:18 p.m.
New subject: [JBoss JIRA] Resolved: (DNA-505) Svn Repository Source with NPE and other issues while opening connection through Jcr
[
https://jira.jboss.org/jira/browse/DNA-505?page=com.atlassian.jira.plugin...
]
Randall Hauch resolved DNA-505.
-------------------------------
Resolution: Done
I'm marking this as resolved, since we haven't heard from Feu. If this remains a
problem, this issue can be reopened, or a new one can be created.
Svn Repository Source with NPE and other issues while opening
connection through Jcr
------------------------------------------------------------------------------------
Key: DNA-505
URL: https://jira.jboss.org/jira/browse/DNA-505
Project: DNA
Issue Type: Bug
Components: Connectors
Affects Versions: 0.6
Environment: Mac OS X 10.5 - Jvm 1.5 - Maven 2
Reporter: Luiz Fernando Teston
Assignee: Randall Hauch
Fix For: 0.6
Attachments: 0001-fixing-a-few-null-pointer-exeptions.patch,
DnaSvnUsingJcrWithProgramaticConfigurationTest.java
Durring a test run to read data from some svn repository using Jcr api from DNA, it
throws NullPointerException when trying to read jcr:content for nodes of type folder. This
NPEs was really easy to solve. So, I created a patch for this. After this patch, when
running the same unit test, it throws a repository source exception saying
"svnRepositorySource does not allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java""
workspace".
The stack trace is here also:
org.jboss.dna.graph.connector.RepositorySourceException: svnRepositorySource does not
allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.checkThePath(SVNRepositoryRequestProcessor.java:1000)
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:151)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:641)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:239)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
at
org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:176)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:314)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:38 a.m.
New subject: [JBoss JIRA] Commented: (DNA-505) Svn Repository Source with NPE and other issues while opening connection through Jcr
[
https://jira.jboss.org/jira/browse/DNA-505?page=com.atlassian.jira.plugin...
]
Luiz Fernando Teston commented on DNA-505:
------------------------------------------
Since the original problem (NPE) was solved, I just created the issue DNA-519 for the
performance issues on Svn Connector.
Svn Repository Source with NPE and other issues while opening
connection through Jcr
------------------------------------------------------------------------------------
Key: DNA-505
URL: https://jira.jboss.org/jira/browse/DNA-505
Project: DNA
Issue Type: Bug
Components: Connectors
Affects Versions: 0.6
Environment: Mac OS X 10.5 - Jvm 1.5 - Maven 2
Reporter: Luiz Fernando Teston
Assignee: Randall Hauch
Fix For: 0.6
Attachments: 0001-fixing-a-few-null-pointer-exeptions.patch,
DnaSvnUsingJcrWithProgramaticConfigurationTest.java
Durring a test run to read data from some svn repository using Jcr api from DNA, it
throws NullPointerException when trying to read jcr:content for nodes of type folder. This
NPEs was really easy to solve. So, I created a patch for this. After this patch, when
running the same unit test, it throws a repository source exception saying
"svnRepositorySource does not allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java""
workspace".
The stack trace is here also:
org.jboss.dna.graph.connector.RepositorySourceException: svnRepositorySource does not
allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.checkThePath(SVNRepositoryRequestProcessor.java:1000)
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:151)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:641)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:239)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
at
org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:176)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:314)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5367
days inactive
5382
days old
16 comments
2 participants
participants (2)
-
Luiz Fernando Teston (JIRA) -
Randall Hauch (JIRA)