I am not very familiar with camel. After analyzing the moqui-camel example, I hope there is an example of building MoquiServiceConsumer as a reference.
The current example generates a producerTemplate through the sd.location pointed to by the camel type in the call service, and calls requestBodyAndHeaders to return the executed TargetCamelExample.
My real question is how to use this moqui component to complete a typical camel function, such as listening to receive a file directory, filtering out files with a csv suffix, making some supplements to the content, and then importing it to the target service.
1 Like
Apache Camel is sort of a message-based scripting tool, or in terms of fitting it into a context you can think of it as calling an async script by sending a message (from a producer) and receiving a response (from a consumer). Any Camel endpoint that can produce or consume certain messages can be configured along with other camel tool, so the Moqui integration with Apache Camel just provides consumer and producer interfaces to the Service Facade.
1 Like
I’m also a bit surprised that moqui-camel provides these interfaces for the purpose of being a camel component? So that it can be called directly in routes in a standalone camel program?
If you think of moqui as a backend service, wouldn’t it achieve the same effect by making it available for camel calls via the RestFul interface? So what is the purpose of moqui-camel?
1 Like