Hello `RemoteBundleContextClientImpl` in the stack trace means that it (the stack trace) comes from client side of the test.
Pax Exam is not difficult if it comes about writing @Test-annotated methods, but it is very difficult when trying to set everything up correctly, so jars not conflict with actual bundles and client/server side of things behaves as expected. In your stack trace you obviously miss the exception class on client-side classpath (when running from Eclipse). To be honest I never run such tests from Eclipse/IDEA, I always run from Maven (surefire/failsafe) and do a remote debugging. You can debug Maven, surefire itself or Karaf container started from surefire (3 separate JVMs involved...). In your case I'd first look at the server side logs - you're running pax-exam-container-karaf, so you should have logs in the Karaf instance started by Pax Exam - don't forget to call org.ops4j.pax.exam.karaf.options.KarafDistributionOption#keepRuntimeFolder() in your Pax Exam configuration method. And to really get org.apache.derby.shared.common.error.DerbySQLIntegrityConstraintViolationException at client side, be sure to have Derby driver on the classpath. regards Grzegorz Grzybek sob., 3 cze 2023 o 18:38 Steinar Bang <s...@dod.no> napisał(a): > Platform: debian 11.7 "bullseye", amd64 > openjdk-17-jdk:amd64 17.0.6+10-1~deb11u1 (ie. java 17) > karaf 4.4.3 > pax-exam 4.13.5 > eclipse 2023-03 (4.27.0) > > I am trying to run a pax exam test that runs a liquibase changelist to > set up a schema and then add a row to a table in that schema and reads > it back out. > > What I'm trying to do is add more asserting to this test to verify that > the database schema was actually created and is working: > > https://github.com/steinarb/liquibase-karaf-feature/blob/master/liquibase-integration-test/karaf.liquibase.tests/src/test/java/no/priv/bang/karaf/liquibase/tests/LiquibaseKarafFeatureIntegrationTest.java#L55 > > When the tests fails in the database I get a classnotfoundexception on > org.apache.derby.shared.common.error.DerbySQLIntegrityConstraintViolationException > and the following stack trace: > https://gist.github.com/steinarb/e80ec79aa66bf48e58e441d172931989 > > Is it possible to get a stack trace for the actual failure, instead of a > stack trace for not finding the exception class (which this seems to > be...?). > > Thanks! > > > - Steinar > > -- > -- > ------------------ > OPS4J - http://www.ops4j.org - ops4j@googlegroups.com > > --- > You received this message because you are subscribed to the Google Groups > "OPS4J" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ops4j+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ops4j/87a5xglcvd.fsf%40dod.no. > -- -- ------------------ OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ops4j/CAAdXmhpukAeoGjhc6iHXr4xDTpEnETb-_M%3DWAgarN0v95z%2Bf-A%40mail.gmail.com.
