Hi Claus,
it still gets me the same error. I am the one actually implementing the PLC4X
Component, so maybe I did a mistake by upgrading to 3.x in the Endpoint
implementation?
Here is the Endpoint:
Hi
Try with
tags=#bean:beanTags
On Wed, Apr 8, 2020 at 2:35 PM Etienne Robinet wrote:
>
> Hi all,
> I have a blueprint that uses a Component (plc4x) to fetch data from a PLC.
> The Consumer need a parameter called "tags" which is a List. In Camel
> 2.24.2, I used to reference the list in
Hi all,
I have a blueprint that uses a Component (plc4x) to fetch data from a PLC. The
Consumer need a parameter called "tags" which is a List. In Camel
2.24.2, I used to reference the list in the uri like this: ...?tags=#beanTags
where I created a Bean outside the context that looked like
On Mon, Apr 6, 2020 at 4:17 PM David Jencks wrote:
>
> I’ve been looking at the tables of components, data formats, etc in the
> website and wondering if it would be useful to show "version deprecated
> since” rather than just the deprecated flag. Is this information even
> available? Does
+1 to David Jencks.
i raised a while ago but coul not start doing anything on it.
https://camel.465427.n5.nabble.com/deprecated-components-by-which-version-of-camel-td5842700.html
it would be a good addition while playing around with models.
On Mon, Apr 6, 2020 at 5:17 PM David Jencks
wrote:
>
Hi
Okay I am moving forward with Peters work, and for starters grab the
supportLevel piece as that is general and a good addition.
I have modified the PR and include 3 levels: Experimental, Preview and Stable.
And made changes so we can specify the level in the pom.xml file, as
that allows to
