No, to my knowledge this is NOT complete :-) as you just provide a PARTIAL snapshot of your Blueprint and then expect people to understand what is going wrong in your App.
Would you mind to share the whole thing with us, example the </blueprint> closing tag is missing by your provided config. Other than that it's a BAD practice to make use of a specific version of a given XSD (you can google for this to find out why) , so a better approach would be: xsi:schemaLocation="http://camel.apache.org/schema/blueprint http://camel.apache.org/schema/blueprint/camel-blueprint.xsd" Babak Maurice wrote > To my knowledge this is complete: > > <?xml version="1.0" encoding="UTF-8"?> > <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:cml="http://camel.apache.org/schema/blueprint" > xsi:schemaLocation="http://camel.apache.org/schema/blueprint > http://camel.apache.org/schema/blueprint/camel-blueprint-2.11.0.xsd"> > > <camelContext xmlns="http://camel.apache.org/schema/blueprint" > id="camelContext" depends-on="logService"> > Claus, what do you mean with order? I have the blueprint split-up in > camel-context, module-context and osgi-context xml files. -- View this message in context: http://camel.465427.n5.nabble.com/Producer-template-and-spring-xml-defaultendpoint-error-tp5737471p5737479.html Sent from the Camel - Users mailing list archive at Nabble.com.