case, from the succer
who got himself fired leaving me to solve his crap, does not require me te
produce multiple messages any more. And the xsd version stays in untill i am
finished developing.
--
View this message in context:
http://camel.465427.n5.nabble.com/Producer-template-and-sprin
ve 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.
osgi-context xml files.
--
View this message in context:
http://camel.465427.n5.nabble.com/Producer-template-and-spring-xml-defaultendpoint-error-tp5737471p5737475.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ma/blueprint":route}' is expected.
>
> Programmatically this works perfect, injecting the camel context in the
> processor and instantiating the template from it.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Producer-te
und starting with element 'template'. One of
> '{"http://camel.apache.org/schema/blueprint":route}' is expected.
>
> Programmatically this works perfect, injecting the camel context in the
> processor and instantiating the template from it.
--
View this me
from it.
--
View this message in context:
http://camel.465427.n5.nabble.com/Producer-template-and-spring-xml-defaultendpoint-error-tp5737471.html
Sent from the Camel - Users mailing list archive at Nabble.com.
