I do usually keep them separate, unless they really need to share context.
Regards.
On Jan 7, 2012 9:54 PM, "Jason Dillon" wrote:
> I'm wondering what the best practice is for a complex application, where
> many sub-systems (some related, some not) are using camel to process
> messages, if it is
I'm wondering what the best practice is for a complex application, where many
sub-systems (some related, some not) are using camel to process messages, if it
is best to have all of them share the same single CamelContext or if its better
to have more than one CamelContext to partition the system
Hallo!
I have tried to use a cookbook article, but this article uses a schema file
which does not exist.
The article can be found here:
http://camel.apache.org/camel-transport-for-cxf.html
And the missing schema file is: http://cxf.apache.org/transports/camel.xsd
Where is this schema file?
And
Hello Claus!
Thanks for sharing this with us. I didn't was aware of this...
Best,
Christian
On Fri, Jan 6, 2012 at 1:39 PM, Claus Ibsen wrote:
> On Thu, Jan 5, 2012 at 10:43 PM, Christian Müller
> wrote:
> > Steven, Gert, did you could have a look at [1].
> >
> > I would like to work/support
There must be something wrong on your side.
Checkout [1]. There you can see the CamelContext has this method.
[1]
https://svn.apache.org/repos/asf/camel/tags/camel-2.9.0/camel-core/src/main/java/org/apache/camel/CamelContext.java
Best,
Christian
Only if you can use the Camel 2.9.1-SNAPSHOT or 2.10.0-SNAPSHOT version.
I will update the wiki page today or tomorrow to document the
changes/improvements which comes with CAMEL-4152.
Best,
Christian
I had to fix camel-stringtemplate, camel-freemaker and camel-velocity in
all supported branches (trunk, camel-2.9.x, camel-2.8.x and camel-2.7.x).
If you cannot use a snapshot version (what I asume), I would propose to use
the enricher component as a workaround. Something like:
from("xxx")
.enri
