Hi Christian, Thanks, I think I glanced at those. Even though we probably should, we are not using CXF. That's a reasonable assumption given my soapUI mention.
Anyhow, I'm pretty much giving up on soapUI tests on top of pax-exam or pax-runner. I got all the services going, but trying to load soapUI into the OSGi container wasn't working. I also abandoned researching using pax-runner in a pre-integration-test/post-integration-test. My last ditch effort involves the following. We have a simple, request/response black-box OSGi service that can be used to front-end the REST services I'm trying to test. However, it's written in Scala and is much easier to consume in Scala. As such, I need to write my Pax Exam unit tests in Scala. However, I can't get the probe to find scala.scalaObject. I have scala-library (with OSGi manifest) in my pom, so I'm not sure what is going on. If I don't abandon this line altogether, I'll take that question to the ops4j list. Of course, if anyone here has an answer/suggestion, I would greatly appreciate it! :) On Sun, Aug 7, 2011 at 4:02 PM, Christian Müller <[email protected]> wrote: > Hello Samuel! > > Did you checked the CXF OSGI test [1]? May it will help. Or do you have to > create your tests with soapUI? > > I'm not sure how easy it is to run the PAX exam tests in the Maven > pre-integration-test phase. But I think it's not so easy and that is the > reason why Camel put/run the OSGI integration tests in its own maven module > and run it in the "normal" test phase. With this it's also easy to skip the > OSGI tests in some situations (may on the local machine and run the OSGI > tests only one time on the CI server because the tests are (currently) > slow). > > [1] > https://svn.apache.org/repos/asf/camel/trunk/tests/camel-itest-osgi/src/test/java/org/apache/camel/itest/osgi/cxf/blueprint/CxfBlueprintRouterTest.java > > Best, > Christian >
