How to avoid importing bunch of cxf packages when start up the camel-cxf endpoint from OSGi platform ?Page added by willem jiangIf you are using camel-cxf endpoint in your OSGi bundle and want to get full of control of CXF component loading. (eg. you just want to use the http jetty transport, soap binding and don't want to load jms transport, jaxrs modules). You may need to tell SpringBusFactory which module should be load, in this way you need to import bunch of cxf packages or using the * on the DynamicImport-Package section of your application's OSGi meta information. As the CXF bundle have the most cxf configuration file, here is a way to do it by setting the right thread context class loader to load the cxf module configures, without any additional setting. NOTE, if you have other CXF configuration which want to be load, you need to make sure the thread context class loader can load it. ClassLoader oldCL = Thread.currentThread().getContextClassLoader(); try { Thread.currentThread().setContextClassLoader( BusFactory.class.getClassLoader()); SpringBusFactory springBusFactory = new SpringBusFactory(); Bus bus = springBusFactory.createBus(new String[] { "META-INF/cxf/cxf.xml", "META-INF/cxf/cxf-extension-soap.xml", "META-INF/cxf/cxf-extension-http-jetty.xml" }, false); // The last parameter is telling CXF not to load the cxf-extension-*.xml from META-INF/cxf // You can set the bus the normal CXF endpoint or other camel-cxf endpoint } finally { Thread.currentThread().setContextClassLoader(oldCL); }
Change Notification Preferences
View Online
|
Add Comment
|
