Big problem with Cactus + jboss 4 + Jackrabbit

[Guillaume BIET <gu...@gmail.com>]

Hi everyone,

I'm lost .... I've got an error :

- <testcase classname="src.TestRemote" name="testCleanProjectRepository" 
time="2.393">
  <failure message="Test Failure : Cannot instantiate persistence manager 
org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager: 
org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager;caused by 
:java.lang.ClassCastException: 
org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager" 
type="org.apache.cactus.internal.client.AssertionFailedErrorWrapper">junit.framework.AssertionFailedError: 
Test Failure : Cannot instantiate persistence manager 
org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager: 
org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager;caused by 
:java.lang.ClassCastException: 
org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager at 
src.TestJCRManagerRemote.testCleanProjectRepository(TestJCRManagerRemote.java:52) 
at 
org.apache.cactus.internal.AbstractCactusTestCase.runBareServer(AbstractCactusTestCase.java:153) 
at 
org.apache.cactus.internal.server.AbstractWebTestCaller.doTest(AbstractWebTestCaller.java:119) 
at 
org.apache.cactus.internal.server.AbstractWebTestController.handleRequest_aroundBody0(AbstractWebTestController.java:93) 
at 
org.apache.cactus.internal.server.AbstractWebTestController.handleRequest_aroundBody1$advice(AbstractWebTestController.java:224) 
at 
org.apache.cactus.internal.server.AbstractWebTestController.handleRequest(AbstractWebTestController.java) 
at 
org.apache.cactus.server.ServletTestRedirector.doPost_aroundBody2(ServletTestRedirector.java:101) 
at 
org.apache.cactus.server.ServletTestRedirector.doPost_aroundBody3$advice(ServletTestRedirector.java:224) 
at 
org.apache.cactus.server.ServletTestRedirector.doPost(ServletTestRedirector.java) 
at 
org.apache.cactus.server.ServletTestRedirector.doGet_aroundBody0(ServletTestRedirector.java:72) 
at 
org.apache.cactus.server.ServletTestRedirector.doGet_aroundBody1$advice(ServletTestRedirector.java:224) 
at 
org.apache.cactus.server.ServletTestRedirector.doGet(ServletTestRedirector.java) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) 
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) 
at 
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) 
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) 
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) 
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) 
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) 
at 
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) 
at 
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) 
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) 
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) 
at 
org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) 
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) 
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) 
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) 
at 
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) 
at 
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) 
at 
org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) 
at java.lang.Thread.run(Thread.java:595)</failure>


The problem is all is done perfectly... I think and hope so !!

Did anyone had this error a day ??? May be he can help me :) I can't find 
the problem...

thanks !


sincerely, 

Does the Cactus test runner enforce an order of execution?

[da...@accenture.com]

All, 
 
When I was running jUnit tests in a TestSuite, the run order of the tests were the order the tests were added to the suite. Now that I am running them with Cactus, the order is not the order the tests were added. 
 
Have others encountered this?
 
David Novogrodsky


This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information.  If you have received it in error, please notify the sender immediately and delete the original.  Any other use of the email by you is prohibited.