What is difference between repository index and workspace index
I just find the index size under repository directory is smaller than the workspace directory.Who can help me understand this.Thanks!
The warn about the full text index of image/gif
I just upload a image to the repository,but it throws a such WARN org.apache.jackrabbit.core.query.lucene.JackrabbitTextExtractor - Full text indexing of image/gif is not supported I think there are some configuration problem.Please give me some advices
Re: [VOTE] Release Apache Jackrabbit 1.2
＋1 2007/1/11, Jukka Zitting <[EMAIL PROTECTED]>: Hi, I have posted a candidate for the Apache Jackrabbit 1.2 release at http://people.apache.org/~jukka/jackrabbit/1.2/ See the included RELEASE-NOTES.txt file for details on release contents and latest changes. The release was made from the 1.2 branch with only minor JCR-686 changes applied after rc2. Please vote on releasing these packages as Apache Jackrabbit 1.2. The vote is open for the next 72 hours, and only votes from Jackrabbit committers are binding. The vote passes if at least three +1 votes are cast. [ ] +1 Release the packages as Apache Jackrabbit 1.2 [ ] -1 Do not release the packages because... BR, Jukka Zitting
Re: The problem in building the jackrabbit-jcr-commons
Oh ,I found the whole project need this file ,not only jackrabbit-jcr-commons module . I think that is related to the maven project.But this is strange problem for building the whole project.You can check in your each driver(just in the root directory) ,Is there a hidden file named "myplay.com"
The problem in building the jackrabbit-jcr-commons
hi ,I met a strange problem when I build the newest version of jackrabbit from svn. I found the jackrabbit-jcr-commons need to read a file "d:\mplay.com". But I find this file maybe a virus.So I delete it ,then there is a error in the building. Now I just give an empty file which called the "mplay.com.bat". Then the building is normal.
Re: Changing affiliations
Congratulation ,and happy new year to all developer in the jackrabbit. 2007/1/2, Paco Avila <[EMAIL PROTECTED]>: El mar, 02-01-2007 a las 10:39 +0200, Jukka Zitting escribió: > Hi, > > After a while of contracting I have now become a full time employee of > Day Software. In practice this change will have little effect on my > work with Apache Jackrabbit and the JSR 283 expert group, except > perhaps by allowing me to spend more time working with JCR. Congratulations and happy new year for all! -- GIT Consultors S.L. c\ Francesc Rover 2-B 07003 Palma de Mallorca (Illes Balears)
Re: The exception about test report
I have update the main source code to the newest version,and My jdk's
version is 1.5.6.The same time I found the test process will terminated
without any response .
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [surefire:test {execution: do_init}]
[INFO] Surefire report directory: F:\jackrabbit1.1\jackrabbit-core\target\surefi
re-reports
---
T E S T S
---
Running org.apache.jackrabbit.init.ExportDocViewTestData
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.797 sec
Running org.apache.jackrabbit.init.PropertyTestData
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec
Running org.apache.jackrabbit.init.NodeTestData
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.079 sec
Running org.apache.jackrabbit.init.QueryTestData
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec
Results :
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
[INFO] [surefire:test {execution: do_test}]
[INFO] Surefire report directory: F:\jackrabbit1.1\jackrabbit-core\target\surefi
re-reports
---
T E S T S
---
Running org.apache.jackrabbit.core.nodetype.compact.TestAll
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.219 sec
Running org.apache.jackrabbit.test.TestAll
Exception in thread "Timer-2" java.lang.NullPointerException
at org.apache.jackrabbit.core.query.lucene.NodeIndexer.createDoc(NodeInd
exer.java:129)
at org.apache.jackrabbit.core.query.lucene.AbstractIndex.addNode(Abstrac
tIndex.java:134)
at org.apache.jackrabbit.core.query.lucene.VolatileIndex.commitPending(V
olatileIndex.java:162)
at org.apache.jackrabbit.core.query.lucene.VolatileIndex.commit(Volatile
Index.java:141)
at org.apache.jackrabbit.core.query.lucene.PersistentIndex.copyIndex(Per
sistentIndex.java:162)
at org.apache.jackrabbit.core.query.lucene.MultiIndex$VolatileCommit.exe
cute(MultiIndex.java:1737)
at org.apache.jackrabbit.core.query.lucene.MultiIndex.executeAndLog(Mult
iIndex.java:804)
at org.apache.jackrabbit.core.query.lucene.MultiIndex.commitVolatileInde
x(MultiIndex.java:852)
at org.apache.jackrabbit.core.query.lucene.MultiIndex.flush(MultiIndex.j
ava:723)
at org.apache.jackrabbit.core.query.lucene.MultiIndex.close(MultiIndex.j
ava:657)
at org.apache.jackrabbit.core.query.lucene.SearchIndex.close(SearchIndex
.java:355)
at org.apache.jackrabbit.core.SearchManager.shutdownQueryHandler(SearchM
anager.java:519)
at org.apache.jackrabbit.core.SearchManager.access$300(SearchManager.jav
a:61)
at org.apache.jackrabbit.core.SearchManager$2.run(SearchManager.java:256
)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Tests run: 1055, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 78.75 sec
Running org.apache.jackrabbit.core.xml.TestAll
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.093 sec
Running org.apache.jackrabbit.core.observation.TestAll
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.485 sec
Running org.apache.jackrabbit.core.query.TestAll
Tests run: 101, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.156 sec
Running org.apache.jackrabbit.core.config.TestAll
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.281 sec
Running org.apache.jackrabbit.core.nodetype.xml.TestAll
Tests run: 34, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.75 sec
Running org.apache.jackrabbit.core.TestAll
Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.953 sec
Running org.apache.jackrabbit.core.state.TestAll
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.032 sec
Running org.apache.jackrabbit.value.TestAll
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec
Results :
Tests run: 1245, Failures: 0, Errors: 0, Skipped: 0
<http://202.106.181.121/Student/gwyfirstpage.aspx>
<http://202.106.181.121/Student/gwyfirstpage.aspx>
<http://202.106.181.121/Student/gwyfirstpage.aspx>
===
2006/12/28, Jukka Zitting <[EMAIL PROTECTED]>:
Hi,
On 12/28/06, wendy Lee <[EMAIL PROTECTED]> wrote:
> The newest version has two exception in SQLPathTest.
I'm not seeing it. Can you double-check with "mvn clean install"? If
the problem continues, please file a bug report for that with your
system details (java version, etc.), the exact revision you have, and
the full surefire report with the failure stack traces.
Note that I recently made some ch
The exception about test report
The newest version has two exception in SQLPathTest. --- testDescendantTestRoot(org.apache.jackrabbit.test.api.query.SQLPathTest) junit.framework.AssertionFailedError: /testdata/serialization is not part of the result set at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.apache.jackrabbit.test.api.query.AbstractQueryTest.checkResult(AbstractQueryTest.java:281) at org.apache.jackrabbit.test.api.query.AbstractQueryTest.executeSqlQuery(AbstractQueryTest.java:258) at org.apache.jackrabbit.test.api.query.SQLPathTest.testDescendantTestRoot(SQLPathTest.java:71) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:393) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) testChildAxisTestRoot(org.apache.jackrabbit.test.api.query.SQLPathTest) junit.framework.AssertionFailedError: /testdata/serialization is not part of the result set at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.apache.jackrabbit.test.api.query.AbstractQueryTest.checkResult(AbstractQueryTest.java:281) at org.apache.jackrabbit.test.api.query.AbstractQueryTest.executeSqlQuery(AbstractQueryTest.java:258) at org.apache.jackrabbit.test.api.query.SQLPathTest.testChildAxisTestRoot(SQLPathTest.java:136) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:393) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) testDescendantTestRoot(org.apache.jackrabbit.test.api.query.SQLPathTest) junit.framework.AssertionFailedError: /testdata/serialization is not part of the result set at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.apache.jackrabbit.test.api.query.AbstractQueryTest.checkResult(AbstractQueryTest.java:281) at org.apache.jackrabbit.test.api.query.AbstractQueryTest.executeSqlQuery(AbstractQueryTest.java:258) at org.apache.jackrabbit.test.api.query.SQLPathTest.testDescendantTestRoot(SQLPathTest.java:71) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.jav
The NullPointerException with the newest version
T E S T S --- Running org.apache.jackrabbit.core.nodetype.compact.TestAll Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.25 sec Running org.apache.jackrabbit.test.TestAll Exception in thread "Timer-2" java.lang.NullPointerException at org.apache.jackrabbit.core.query.lucene.NodeIndexer.createDoc (NodeInd exer.java:129) at org.apache.jackrabbit.core.query.lucene.AbstractIndex.addNode (Abstrac tIndex.java:134) at org.apache.jackrabbit.core.query.lucene.VolatileIndex.commitPending(V olatileIndex.java:162) at org.apache.jackrabbit.core.query.lucene.VolatileIndex.commit (Volatile Index.java:141) at org.apache.jackrabbit.core.query.lucene.PersistentIndex.copyIndex (Per sistentIndex.java:162) at org.apache.jackrabbit.core.query.lucene.MultiIndex$VolatileCommit.exe cute(MultiIndex.java:1737) at org.apache.jackrabbit.core.query.lucene.MultiIndex.executeAndLog (Mult iIndex.java:804) at org.apache.jackrabbit.core.query.lucene.MultiIndex.commitVolatileInde x(MultiIndex.java:852) at org.apache.jackrabbit.core.query.lucene.MultiIndex.flush( MultiIndex.j ava:723) at org.apache.jackrabbit.core.query.lucene.MultiIndex.close( MultiIndex.j ava:657) at org.apache.jackrabbit.core.query.lucene.SearchIndex.close (SearchIndex .java:355) at org.apache.jackrabbit.core.SearchManager.shutdownQueryHandler (SearchM anager.java:519) at org.apache.jackrabbit.core.SearchManager.access$300( SearchManager.jav a:61) at org.apache.jackrabbit.core.SearchManager$2.run(SearchManager.java :256 ) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462)
The test failure with class XATest
anyone can fix this version number bug? Thank you
Re: what wrong when I compile the jackrabbit-core
T E S T S --- Running org.apache.jackrabbit.core.nodetype.compact.TestAll Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.453 sec Running org.apache.jackrabbit.test.TestAll Tests run: 1055, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 154.891sec Running org.apache.jackrabbit.core.xml.TestAll Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.094 sec Running org.apache.jackrabbit.core.observation.TestAll Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.562 sec Running org.apache.jackrabbit.core.query.TestAll Tests run: 101, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 21.594 sec Running org.apache.jackrabbit.core.config.TestAll Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.5 sec Running org.apache.jackrabbit.core.nodetype.xml.TestAll Tests run: 34, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.328 sec Running org.apache.jackrabbit.core.TestAll Tests run: 29, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.516 sec <<< F AILURE! Running org.apache.jackrabbit.core.state.TestAll Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec Running org.apache.jackrabbit.value.TestAll Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.063 sec Results : Tests run: 1245, Failures: 1, Errors: 0, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. [INFO] [INFO] Trace org.apache.maven.BuildFailureException: There are test failures. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (Defa ultLifecycleExecutor.java:555) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (Defau ltLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLi fecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java :315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java :430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures . at org.apache.maven.plugin.surefire.SurefirePlugin.execute (SurefirePlugi n.java:403) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPlugi nManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (Defa ultLifecycleExecutor.java:534) ... 16 more [INFO] [INFO] Total time: 4 minutes 2 seconds [INFO] Finished at: Sat Dec 16 19:45:38 CST 2006 [INFO] Final Memory: 6M/21M [INFO] I use mvn clean ,but nothing changed . how I can skip it.
Re: what wrong when I compile the jackrabbit-core
Yes I also have this problem ... --- Test set: org.apache.jackrabbit.core.TestAll --- Tests run: 29, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.14 sec <<< FAILURE! testXAVersionsThoroughly(org.apache.jackrabbit.core.XATest) Time elapsed: 0.234 sec <<< FAILURE! junit.framework.ComparisonFailure: checkin N1 uncommitted. Version Name expected:<...1...> but was:<...0...> at junit.framework.Assert.assertEquals(Assert.java:81) at org.apache.jackrabbit.core.XATest.check(XATest.java:1140) at org.apache.jackrabbit.core.XATest.testXAVersionsThoroughly( XATest.java:1080)
Re: what wrong when I compile the jackrabbit-core
Thank you ,resolve it
what wrong when I compile the jackrabbit-core
I just update the source code to newest version ,when I run mvn install .there are some error in the test . --- T E S T S --- Running org.apache.jackrabbit.init.ExportDocViewTestData Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.109 sec <<< FA ILURE! Running org.apache.jackrabbit.init.PropertyTestData Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.063 sec <<< FA ILURE! Running org.apache.jackrabbit.init.NodeTestData Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.046 sec <<< FA ILURE! Running org.apache.jackrabbit.init.QueryTestData Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.047 sec <<< FA ILURE! Results : Tests run: 4, Failures: 0, Errors: 4, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. [INFO] [INFO] Trace org.apache.maven.BuildFailureException: There are test failures. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (Defa ultLifecycleExecutor.java:555) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (Defau ltLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLi fecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java :315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java :430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures . at org.apache.maven.plugin.surefire.SurefirePlugin.execute (SurefirePlugi n.java:403) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPlugi nManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (Defa ultLifecycleExecutor.java:534) ... 16 more [INFO] [INFO] Total time: 19 seconds [INFO] Finished at: Tue Dec 12 20:00:38 CST 2006 [INFO] Final Memory: 7M/21M [INFO]
Re: [jira] Resolved: (JCR-651) Improve performance for queries with large result sets
Thank you for your detail help
Re: [jira] Resolved: (JCR-651) Improve performance for queries with large result sets
If I use this config & set resultFetchSize to 50 , When I use "count = result.getNodes().getSize()" the count is 50?or the total amount in the query condition?
Re: HEADS UP: Jackrabbit restructuring ahead
and now I can build it .I don't know if it is a small flaw in the
pom.xmlunder jackrabbit-core
...
org.apache.jackrabbit
jackrabbit-commons
${pom.version}
I modify it to this.
org.apache.jackrabbit
jackrabbit-jcr-commons
${pom.version}
Re: HEADS UP: Jackrabbit restructuring ahead
I checkout the jackrabbit-api &jackrabbit-jcr-commons&jackrabbit-core&jackrabbit-jcr-tests separately and under each directory I use command "mvn install" ,at last under the directory of jackrabbit-core .when I use mvn install . [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.jackrabbit ArtifactId: jackrabbit Version: 1.2-SNAPSHOT Reason: Unable to download the artifact from any repository org.apache.jackrabbit:jackrabbit:pom:1.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 9 seconds [INFO] Finished at: Mon Dec 04 12:54:21 CST 2006 [INFO] Final Memory: 11M/20M [INFO]
Re: HEADS UP: Jackrabbit restructuring ahead
I not familiar with maven ..At primary I use maven 1.0.2 ,Now I update it to 2.0.4 .and follow your description , I change my local url to "/trunk/jackrabbit-core" ( I worked in the /trunk/jackrabbit ) . I update my directory and found the test codes remove from my local directory . Now I want to know how I can re-build the source code in local .Do I need to get all source code from trunk?
Re: [VOTE] Release Apache Jackrabbit 1.1.1
[x]+1 Release the packages as Apache Jackrabbit 1.1.1
Re: can I reindex a whole repository?
I want to make sure if I remove the indexes directory in the repository ? or just remove index directory in the workspace directory? 2006/11/23, Paco Avila <[EMAIL PROTECTED]>: El mié, 22-11-2006 a las 19:08 +0100, Tobias Bocanegra escribió: > yes, > - stop the repository > - delete the search indexes in the workspace directories > - start the repository > > the search handler will then traverse the repository and reindex all items. > regards, toby Do you mean delete "index" or delete "index/*"? > btw: this sort of questions rather belongs to the user list than to > the dev list. more or less, but an (low level) API that reindex an document or the whole repository should be nice :) -- Paco Avila <[EMAIL PROTECTED]>
Re: Is this a bug of derby database or Jackrabbit?
This is derby log 2006-11-09 09:02:38.429 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.2.1.6 - (452058): instance c013800d-010e-cbf4-578c-1ed50590 on database directory /opt/weekee-R8.8/repository/version/db Database Class Loader started - derby.database.classpath='' 2006-11-09 09:02:40.911 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.2.1.6 - (452058): instance 787c0020-010e-cbf4-578c-1ed50590 on database directory /opt/weekee-R8.8/repository/workspaces/default/db Database Class Loader started - derby.database.classpath=''
Is this a bug of derby database or Jackrabbit?
The size of our repository reached 14GB ,Now we found the repository can't work normally,and throw many exceptions .The exception like this: 377575 [btpool2-21] ERROR org.apache.jackrabbit.core.state.db.DatabasePersistenceManager - failed to check existence of node state: db364aa7-87be-499e-877d-ed336e938f97 java.sql.SQLException: No current connection. at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.checkStatus(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.setString(Unknown Source) at org.apache.jackrabbit.core.state.db.DatabasePersistenceManager.exists (DatabasePersistenceManager.java:712) at org.apache.jackrabbit.core.state.SharedItemStateManager.hasNonVirtualItemState (SharedItemStateManager.java:878) at org.apache.jackrabbit.core.state.SharedItemStateManager.hasItemState( SharedItemStateManager.java:269) at org.apache.jackrabbit.core.state.LocalItemStateManager.hasItemState( LocalItemStateManager.java:179) at org.apache.jackrabbit.core.state.SessionItemStateManager.hasItemState (SessionItemStateManager.java:186) at org.apache.jackrabbit.core.query.lucene.ConsistencyCheck.run( ConsistencyCheck.java:167) at org.apache.jackrabbit.core.query.lucene.ConsistencyCheck.run( ConsistencyCheck.java:94) at org.apache.jackrabbit.core.query.lucene.SearchIndex.doInit( SearchIndex.java:234) at org.apache.jackrabbit.core.query.AbstractQueryHandler.init( AbstractQueryHandler.java:44) at org.apache.jackrabbit.core.SearchManager.initializeQueryHandler( SearchManager.java:524) at org.apache.jackrabbit.core.SearchManager.(SearchManager.java :268) at org.apache.jackrabbit.core.RepositoryImpl.getSystemSearchManager( RepositoryImpl.java:578) at org.apache.jackrabbit.core.RepositoryImpl.access$300( RepositoryImpl.java:90) at org.apache.jackrabbit.core.RepositoryImpl$WorkspaceInfo.getSearchManager( RepositoryImpl.java:1521) at org.apache.jackrabbit.core.RepositoryImpl.initWorkspace( RepositoryImpl.java:558) at org.apache.jackrabbit.core.RepositoryImpl.(RepositoryImpl.java :255) at org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java :498) at com.hongrui.weekee.service.util.CmsRepoUtil.obtainRepository( CmsRepoUtil.java:31) at com.hongrui.weekee.service.util.CmsRepoUtil.loginToRepository( CmsRepoUtil.java:42) at com.hongrui.weekee.service.util.CmsRepoUtil.loginToRepository( CmsRepoUtil.java:51) at com.hongrui.weekee.service.reading.CmsResourceReader.getMimeType( CmsResourceReader.java:123) at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setMimeTypeForReader (AbstractProcessingPipeline.java:627) at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.processReader (AbstractProcessingPipeline.java:688) at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process( AbstractProcessingPipeline.java:472) at org.apache.cocoon.components.treeprocessor.sitemap.ReadNode.invoke( ReadNode.java:84) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes (AbstractParentProcessingNode.java:46) at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke (PreparableMatchNode.java:130) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes (AbstractParentProcessingNode.java:68) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke( PipelineNode.java:142) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes (AbstractParentProcessingNode.java:68) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke( PipelinesNode.java:92) at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process( ConcreteTreeProcessor.java:234) at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process( ConcreteTreeProcessor.java:176) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process( TreeProcessor.java:248) at org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke( MountNode.java:117) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes (AbstractParentProcessingNode.java:46) at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke (PreparableMatchNode.java:130) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes (AbstractParentProcessingNode.java:68) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke( PipelineNode.java:142) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes (AbstractParentProcessingNod
Is there any solution to solve the pagination in the repostitory
Our application need do pagination for the content in the repository ,such as the "top" keyword in database.I don't know the jackrabbit supply such mechanism.Now we solve this problem by querying repostioty according to every request,But this is very inefficient . Thank you for your help.
Re: [jira] Commented: (JCR-623) Clustering
Do you have any detail in configuration about clustering?such as the repository model. 2006/11/7, Dominique Pfister (JIRA) <[EMAIL PROTECTED]>: [ http://issues.apache.org/jira/browse/JCR-623?page=comments#action_12447461] Dominique Pfister commented on JCR-623: --- Initial commit: 471766 Features still missing: - Automatic archival of journal log entries to save space - Using a database as backend for the journal > Clustering > -- > > Key: JCR-623 > URL: http://issues.apache.org/jira/browse/JCR-623 > Project: Jackrabbit > Issue Type: New Feature > Components: core >Reporter: Dominique Pfister > Assigned To: Dominique Pfister > > Implement basic clustering, i.e. make two or more repositories available at the same time, allowing them to stay in sync with changes applied to only one of them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
The problem about jackrabbit in Jboss
Are there anyone try to config Jboss and deploy jackrabbit in it for clustering? I need some help about this.Thank you.
Re: [jira] Commented: (JCR-595) Refactoring of the Persistence Managers
That's great ,The bug has been fixed .Thank you. 2006/11/1, Jukka Zitting (JIRA) <[EMAIL PROTECTED]>: [ http://issues.apache.org/jira/browse/JCR-595?page=comments#action_12445968] Jukka Zitting commented on JCR-595: --- The "unknown schema" problem should now really be fixed as of revision 469571. The compatibility classes in o.a.j.core.state.db used to override the getClass().getResourceAsStream() call with super.getClass().getResourceAsStream(), so my fix with DatabasePersistenceManager.class.getResourceAsStream() didn't have any effect on the compatibility classes. While the super.getClass() approach is intuitive, it's actually incorrect since super.getClass() is exactly the same as this.getClass() as long as the getClass() method is not overridden. So even if the subclasses attempted to avoid this problem, they actually ended up masking the real solution. The change in revision 469571 removes these workarounds, so that my original fix actually works. > Refactoring of the Persistence Managers > --- > > Key: JCR-595 > URL: http://issues.apache.org/jira/browse/JCR-595 > Project: Jackrabbit > Issue Type: Improvement > Components: core >Reporter: Tobias Bocanegra > Assigned To: Tobias Bocanegra >Priority: Minor > Fix For: 1.2 > > Attachments: jackrabbit.465518.patch > > > currently the persistence managers reside in: > org.apache.jackrabbit.core.state > org.apache.jackrabbit.core.state.db > org.apache.jackrabbit.core.state.mem > org.apache.jackrabbit.core.state.obj > org.apache.jackrabbit.core.state.xml > (org.apache.jackrabbit.core.state.util) > there are also a lot of other classes that deal with states (eg: > SharedItemStateManager) in the state package that do not relate to > pms. > i would like to move all persistencemanagers and pm related stuff to: > org.apache.jackrabbit.core.persistence > I'd keep the current classes as deprecated subclasses within > jackrabbit-core.jar until Jackrabbit 2.0. There may (?) be people who > are extending the existing classes, so I'd avoid breaking binary > compatibility there even though we've never promised to actually honor > compatiblity within o.a.j.core. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Commented: (JCR-595) Refactoring of the Persistence Managers
I just update the version to 469481 ,The problem still exist 2006/10/31, Jukka Zitting (JIRA) <[EMAIL PROTECTED]>: [ http://issues.apache.org/jira/browse/JCR-595?page=comments#action_12445896] Jukka Zitting commented on JCR-595: --- > Configuration error: unknown schema 'derby' This was caused by the use of getClass().getResourceAsStream() to load the DDL files. The resources are local to the o.a.j.core.persistence.dbpackage, so the call failed when invoked from a compatibility subclass in o.a.j.core.state.db. I just committed (revision 469481) a simple fix that replaces getClass() with DatabasePersistenceManager.class. > Refactoring of the Persistence Managers > --- > > Key: JCR-595 > URL: http://issues.apache.org/jira/browse/JCR-595 > Project: Jackrabbit > Issue Type: Improvement > Components: core >Affects Versions: 1.1.1 >Reporter: Tobias Bocanegra > Assigned To: Tobias Bocanegra >Priority: Minor > Fix For: 1.1.1 > > Attachments: jackrabbit.465518.patch > > > currently the persistence managers reside in: > org.apache.jackrabbit.core.state > org.apache.jackrabbit.core.state.db > org.apache.jackrabbit.core.state.mem > org.apache.jackrabbit.core.state.obj > org.apache.jackrabbit.core.state.xml > (org.apache.jackrabbit.core.state.util) > there are also a lot of other classes that deal with states (eg: > SharedItemStateManager) in the state package that do not relate to > pms. > i would like to move all persistencemanagers and pm related stuff to: > org.apache.jackrabbit.core.persistence > I'd keep the current classes as deprecated subclasses within > jackrabbit-core.jar until Jackrabbit 2.0. There may (?) be people who > are extending the existing classes, so I'd avoid breaking binary > compatibility there even though we've never promised to actually honor > compatiblity within o.a.j.core. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Commented: (JCR-595) Refactoring of the Persistence Managers
Yes I have met the same problem with it .How to solve it ? 2006/10/31, Przemo Pakulski (JIRA) <[EMAIL PROTECTED]>: [ http://issues.apache.org/jira/browse/JCR-595?page=comments#action_12445876] Przemo Pakulski commented on JCR-595: - DatabasePersistenceManagers kept for compatibility (in old org.apache.jackrabbit.core.state.db package) doesn't work longer. Following exception is thrown during initailization of repository (file with schema cannot be found) : Testcase: testFillInSearchData(org.apache.jackrabbit.init.QueryTestData): Caused an ERROR Failed to get Repository instance.: javax.jcr.RepositoryException: Cannot instantiate persistence manager org.apache.jackrabbit.core.state.db.DerbyPersistenceManager: Configuration error: unknown schema 'derby': Configuration error: unknown schema 'derby' javax.jcr.RepositoryException: Failed to get Repository instance.: javax.jcr.RepositoryException: Cannot instantiate persistence manager org.apache.jackrabbit.core.state.db.DerbyPersistenceManager: Configuration error: unknown schema 'derby': Configuration error: unknown schema 'derby': javax.jcr.RepositoryException: Cannot instantiate persistence manager org.apache.jackrabbit.core.state.db.DerbyPersistenceManager: Configuration error: unknown schema 'derby': Configuration error: unknown schema 'derby' at org.apache.jackrabbit.test.RepositoryHelper.getRepository( RepositoryHelper.java:70) at org.apache.jackrabbit.test.RepositoryHelper.getProperty( RepositoryHelper.java:150) at org.apache.jackrabbit.test.AbstractJCRTest.getProperty( AbstractJCRTest.java:429) at org.apache.jackrabbit.test.AbstractJCRTest.setUp( AbstractJCRTest.java:254) at org.apache.jackrabbit.test.AbstractJCRTest.run( AbstractJCRTest.java:393) Caused by: org.apache.jackrabbit.test.RepositoryStubException: javax.jcr.RepositoryException: Cannot instantiate persistence manager org.apache.jackrabbit.core.state.db.DerbyPersistenceManager: Configuration error: unknown schema 'derby': Configuration error: unknown schema 'derby' at org.apache.jackrabbit.core.JackrabbitRepositoryStub.getRepository( JackrabbitRepositoryStub.java:112) at org.apache.jackrabbit.test.RepositoryHelper.getRepository( RepositoryHelper.java:68) ... 15 more org.apache.jackrabbit.test.RepositoryStubException: javax.jcr.RepositoryException: Cannot instantiate persistence manager org.apache.jackrabbit.core.state.db.DerbyPersistenceManager: Configuration error: unknown schema 'derby': Configuration error: unknown schema 'derby' at org.apache.jackrabbit.core.JackrabbitRepositoryStub.getRepository( JackrabbitRepositoryStub.java:112) at org.apache.jackrabbit.test.RepositoryHelper.getRepository( RepositoryHelper.java:68) at org.apache.jackrabbit.test.RepositoryHelper.getProperty( RepositoryHelper.java:150) at org.apache.jackrabbit.test.AbstractJCRTest.getProperty( AbstractJCRTest.java:429) at org.apache.jackrabbit.test.AbstractJCRTest.setUp( AbstractJCRTest.java:254) at org.apache.jackrabbit.test.AbstractJCRTest.run( AbstractJCRTest.java:393) > Refactoring of the Persistence Managers > --- > > Key: JCR-595 > URL: http://issues.apache.org/jira/browse/JCR-595 > Project: Jackrabbit > Issue Type: Improvement > Components: core >Affects Versions: 1.1.1 >Reporter: Tobias Bocanegra > Assigned To: Tobias Bocanegra >Priority: Minor > Fix For: 1.1.1 > > Attachments: jackrabbit.465518.patch > > > currently the persistence managers reside in: > org.apache.jackrabbit.core.state > org.apache.jackrabbit.core.state.db > org.apache.jackrabbit.core.state.mem > org.apache.jackrabbit.core.state.obj > org.apache.jackrabbit.core.state.xml > (org.apache.jackrabbit.core.state.util) > there are also a lot of other classes that deal with states (eg: > SharedItemStateManager) in the state package that do not relate to > pms. > i would like to move all persistencemanagers and pm related stuff to: > org.apache.jackrabbit.core.persistence > I'd keep the current classes as deprecated subclasses within > jackrabbit-core.jar until Jackrabbit 2.0. There may (?) be people who > are extending the existing classes, so I'd avoid breaking binary > compatibility there even though we've never promised to actually honor > compatiblity within o.a.j.core. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
index file problem about jackrabbit
Hi,I config the jackrabbit as an application in the Jetty under Linux system ,I trace the process of Jetty access log by command lsof .I find there are many messages such as "java13526 root 104r REG8,1 178635 901304 /opt/weekee-R8.8/repository/repository/index/_jf/_1.cfs (deleted) ,java13526 root 107r REG8,188831 983146 /opt/weekee-R8.8/repository/repository/index/_jq/_1.cfs (deleted)" . I think the problem is the lucene merge index file ,but it doesn't release the index file descriptor. I try to upgrade the lucene jar from 1.4.3 to 2.0,but the compatibility problem is coming. So I need your help to solve this problem .Thank you. Wendeng 2006.10.29
