Dario Malks created PLC4X-316:
-
Summary: DeltaV traffic capture
Key: PLC4X-316
URL: https://issues.apache.org/jira/browse/PLC4X-316
Project: Apache PLC4X
Issue Type: Wish
Components:
+1 yes lets ask on their mailing list if they are interested.
Am Di., 28. Sept. 2021 um 18:32 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:
> Hi all,
>
> at this year's ApacheCOn@Home I attended a talk on Apache Camel and was
> pretty impressed by their component library and Kamelet
Hi all,
at this year's ApacheCOn@Home I attended a talk on Apache Camel and was pretty
impressed by their component library and Kamelet catalog.
However PLC4X is not listed in these as the PLC4X Camel connector is not part
of the Apache Camel project.
What do you folks think about bringing the
Another thought I had last night ... while sort of not being able to sleep (at
least it hat something good)
So I think a "try" field should always be an optional field. As it might be set
or not, just with the difference that the condition is different.
This got me thinking even further ...
BUILD-STABLE: Job 'PLC4X/PLC4X/develop [develop] [643]':
Is back to normal.
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [642]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/642/;>PLC4X/PLC4X/develop
[develop] [642]"
Looks all good to me, and I agree with your both.
On note to option 2: When you look at it from a generic perspective this is
more like a batch-set-property were you set "some" property (endianess is one
of them) for a batch of fields. So I could imaging such batch-attribute-setting
later down
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [641]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/641/;>PLC4X/PLC4X/develop
[develop] [641]"
