Hello All,
I am using camel RestDSL to get Json and conver it to pojo by
.post().type(Schema.class)
but i got below exception
org.apache.camel.InvalidPayloadException: No body available of type:
java.io.InputStream but has value: < *srroy i need to hide package name
here* >Schema
below is the s
Hi
The ejb component extends the bean component, so you can do what the
bean component supports. In the method you can specify the parameters
separated by comma
https://camel.apache.org/components/latest/bean-component.html
https://camel.apache.org/manual/latest/bean-binding.html
So if the body i
Hi,
the migration says
"Support for multiple CamelContexts has been removed and only 1 CamelContext per
deployment is supported."
The term "deployment" seem loose.
My concern here is that in OSGi each bundle has its own CamelContext (e.g. via
blueprint configuration), how will that work?
- M
Hi,
In OSGI,
Each blueprint file equal 1 deployment. So you can put 1 Camel Context by
deployment file.
Example: File deploy_xxx-0.0.1.xml
===
http://www.osgi.org/xmlns/blueprint/v1.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:cm="http://ari
Hi,
Most of the time, you have one bundle (blueprint, scr, ...) == one camel
context.
Technically speaking, you can have several camel contexts in the same
bundle (for instance several blueprint XML, or service).
You can take a look on the Karaf camel examples.
Regards
JB
On 27/08/2021 16:5
Hi!
It looks like we already have "Bindings" but it was deprecated
https://docs.openshift.com/container-platform/3.7/rest_api/api/v1.Binding.html
On Fri, Aug 20, 2021 at 6:18 AM Claus Ibsen wrote:
> Hi
>
> Yeah one of the hardest problem is naming, and after that renaming as
> a lot of old stuf
