Just to give some feedback and closure from my question a whole ago, I
ended up just using a JMS queue to message between the different contexts.
It worked fine, so thank you for letting me know that I should do things
another way. Since the latest documentation describes how to use the VM
Hi, Claus. Thank you for your reply and for your feedback on my current
implementation. I am willing to change it to be simpler/easier/more
foolproof. What transport would you suggest that I use? I would be fine
with switching to a JMS queue, or some other component. I still need to
continue
Hi
You would need more JARs than just camel-core, such as camel-vm etc as
well, and many others.
And this is really IMHO a bad practice on tomcat to mess with
classloading using this shared lib.
On Thu, Aug 6, 2020 at 4:46 PM Steve973 wrote:
>
> We have an application stack, deployed in
We have an application stack, deployed in Tomcat, that consists of several
Spring Boot applications. As part of our operations, we want to send some
messages to a vm endpoint, where a camel route will consume those messages
and then publish them to a JMS topic for any of the other Spring Boot
