ah, good point, that should be this case. Anyway, Option 2 I mentioned before should be good for you, in your customer bundle still use spring-beans.xsd, but never complain can't download it, right? It's because spring-beans bundle contain the local xsd file and use spring.schemas to map to use the local xsd files, more importantly spring-beans bundle start level is 30 which means it can start at earlier stage. So adjust cxf-bundle start level can ensure we use same mechanism with spring-beans. I've already create an issue[1] on cxf side and fixed it, so next servicemix release can pick it up. So for you can manually edit the cxf features.xml to ensure cxf-bundle has less start level.
Also I think there's "Option 3", actually in your customer bundle you can host the necessary xsd files, and add spring.shemas and spring.handlers to specify to use local xsd files from your bundle, I've create a testcase which is based on your test-spring-cxf-rs, basically I just add some files like ./src/main/resources/META-INF/spring.handlers ./src/main/resources/META-INF/spring.schemas ./src/main/resources/schemas ./src/main/resources/schemas/configuration ./src/main/resources/schemas/configuration/cxf-beans.xsd ./src/main/resources/schemas/jaxrs.xsd It works for your current testcase, if your testcase evolve more complex and need more xsd files, than you need add necessary xsd files accordingly. Probably "Option 3" is too much for now, I just append here to demonstrate how your customer bundle can control to load all necessary xsds from itself. [1]https://issues.apache.org/jira/browse/CXF-3979 Freeman http://servicemix.396122.n5.nabble.com/file/n5084928/test-spring-cxf-rs.tar test-spring-cxf-rs.tar -- View this message in context: http://servicemix.396122.n5.nabble.com/Problem-on-use-cxf-on-offline-environment-on-smx-4-4-x-tp5081157p5084928.html Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
