Hi Christian,
I think the better solution is start the CXF server once in the
@BeforeClass method.
If you take a look the unit tests of camel-cxf, we will find there are
lots of tests still use Camel JUnit helper class :)
Willem
----------------------------------
Apache Camel, Apache CXF committer
Open SOA http://www.fusesource.com
Blog http://willemjiang.blogspot.com
Tiwtter http://twitter.com/willemjiang
Christian Müller wrote:
Hello Christian, hello Willem!
I extract the creation of the client in a 'setUpBeforeClass' method, so that
the client is only initialized once:
@BeforeClass
public static void setUpBeforeClass() throws Exception {
URL wsdlURL =
IncommingRouteTest.class.getClassLoader().getResource("META-INF/wlsi/person-non-wrapper.wsdl");
PersonService ss = new PersonService(wsdlURL, new QName("
http://camel.apache.org/non-wrapper";, "PersonService"));
client = ss.getSoap();
}
But I still have the same behavior (because of the reason Willem mentioned).
My knowledge is, that the Camel JUnit helper classes always create a new
camel context after each test. This means for my test, I can not use the
Camel JUnit helper classes?
Regards,
Christian
