Mixing Junit & Cactus tests - but wanting to run from client with minimal classpath

[Marcus Howarth]

Howdy ranchers,
This is starting to do my head in - can anyone help me out please?
I am testing calls on an interface which can be called directly using a ****client.jar that we give out for use with this product.
This interface/jar however has limited functionality - so when it comes to doing some setUp() dataloading type stuff I go direct to the servers EJBs using cactus calls. So far so good.
However, I want to have this test my client jar aswell, so when I run my junit I don't want to include anything my classpath that the client shouldn't have (my core application for example)
So the suite is looking like

  
        // use a cactus test to do our loading of data - calling core calls
        // direct to EJBs that are not included in the classpath
suite.addTest(util.LoadAPIBaseData.suite());

// then these junit tests cover the API
        suite.addTest(api.XXXXTest.suite());
suite.addTest(api.YYYYTest.suite());
....

As the cactus tests are running in the container they will see the classpath on the AS surely, so what is junit complaining about ???

 Failed to invoke suite():java.lang.NoClassDefFoundError: com/company/product/corebitofsystemidontwantanyonetosee/mypackage/MyClass 

Any ideas or pointers appreciated - cheers

[Marcus Howarth]

Came back to it eventually - doesn't seem possible

Please note that the different options for configuring Cactus works both for Cactus client side (i.e. from where you start the JUnit Test Runner) and for the Cactus server side (i.e. from where you start your application server).

see http://jakarta.apache.org/cactus/integration/howto_config.html
never mind - onto plan B....