Looks like a JIRA had already been created. Claus wasn't a big fan of the
change.
https://issues.apache.org/jira/browse/CAMEL-5858
I might try to create a patch and see if there will still be resistance. I
can't imagine I'm the only one with a use case of centralized CamelContext
Wrong mailing list?
--
View this message in context:
http://camel.465427.n5.nabble.com/Apache-crashing-leading-to-all-requsts-being-sent-to-var-apache2-htdocs-tp5760427p5760429.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I believe I have figured it out.
The equivalent of:
camel:camelContext id=AbstractCamelContext
allowUseOriginalMessage=false shutdownRunningTask=CompleteAllTasks
camel:contextScan/
/camel:camelContext
Is:
bean id=AbstractCamelContext
Actually the context didn't start. I'll update here once I figure it out.
In the meantime, any help is appreciated.
--
View this message in context:
http://camel.465427.n5.nabble.com/FW-Spring-Camel-Parent-Context-tp5760339p5760345.html
Sent from the Camel - Users mailing list archive at
There is a spring.handlers file in META-INF that references
org.apache.camel.spring.handler.CamelNamespaceHandler. This is the link
between the Spring Tag and the construction on the implementation classes.
However, I'm still missing a step in the definition that will cause the
Context to start
I got farther with this.
bean id=MyCamelContext
class=org.apache.camel.spring.CamelContextFactoryBean
property name=id value=MyCamelContext /
property name=allowUseOriginalMessage value=false /
property name=shutdownRunningTask
