[
https://issues.apache.org/jira/browse/CAMEL-17319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-17319.
---------------------------------
Resolution: Fixed
spring boot is auto generated
> camel-milo: Add support for Eclipse Milo browsing functionality
> ---------------------------------------------------------------
>
> Key: CAMEL-17319
> URL: https://issues.apache.org/jira/browse/CAMEL-17319
> Project: Camel
> Issue Type: New Feature
> Components: camel-milo
> Reporter: Andreas Klug
> Priority: Major
> Fix For: 3.15.0
>
>
> Hello,
> Currently the Camel-Milo component allows to retrieve node values via OPC-UA
> by specifying explicitly the node ids to be retrieved, meaning, Camel has to
> be aware of the node ids, e. g. by means of configuration.
> However, in case of really large installations, plants, factories, with
> thousands of equipment pieces, that list of node ids is hard to maintain, not
> only because number of the node ids, also due to the fact that this list
> might be very volatile, e. g. a technican changing a water pump counter
> within the plant.
> The Eclipse Milo framework provides a browsing functionality to solve such
> scenarios and it would be very helpful for us if Camel can support this
> existing browsing functionality.
> To support it, I do have a working implementation, which I would like to
> submit as a pull request to discuss it with you, if you're interested in that
> functionality. However, I'm not sure if I did it the right way, e. g.
> * The functionality is implemented as a dedicated component, whereas I
> thought it might be better to have it just as an additional endpoint, but I
> wasn't able to find an example with one component and two Endpoints, which
> differ significantly in configuration, nor was I able to get the
> implementation running that way.
> * I'm not sure how to allow a Spring boot-based configuration
> Would be great if you can provide me with feedback or hints on that.
> I won't be available until next year, at least not for larger parts, but I
> would like to continue in January.
> Thanks!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
