You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Xavier Gagnon <xg...@cogiscan.com> on 2026/05/21 19:46:57 UTC
camel-milo - Support Custom DataTypes
Hello everyone,
The camel-milo OPC UA Client works well to read and write built-in OPC UA DataTypes, but it doesn't seem to work with custom ones. The client is able to read the value from a node with a custom DataType and return it as an ExtensionObject, but we can't actually decode it without having access to the internal milo OpcUaClient's EncodingContexts (and we can't also encode it when trying to write the value).
I don't know if the camel client should be the one doing the decoding/encoding of custom DataTypes. It might be difficult or even impossible for it to correctly determine which EncodingContext to use for encoding/decoding values. But if the milo OpcUaClient could be accessed from outside the internal Camel classes, the user could get its EncodingContexts and do it themselves.
Is it possible to expose the milo OpcUaClient object or its staticEncodingContext and dynamicEncodingContext fields?
Best Regards,
Xavier
The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email by mistake, please notify the sender immediately and do not disclose the contents to anyone or make copies thereof. | Le contenu de ce courriel et de toute pièce jointe est confidentiel. Ils sont destinés uniquement au(x) destinataire(s) nommé(s). Si vous avez reçu ce courriel par erreur, veuillez en informer immédiatement l'expéditeur et ne pas en divulguer le contenu à quiconque, ni en faire des copies.
Re: camel-milo - Support Custom DataTypes
Posted by Andrea Cosentino <an...@gmail.com>.
Hello,
I just opened: https://github.com/apache/camel/pull/23456
The issue is CAMEL-23600
Il giorno ven 22 mag 2026 alle ore 09:45 Aurelien Pupier via users <
users@camel.apache.org> ha scritto:
> Hello,
>
> I'm not very familiar with the internals of the Milo component but this
> request seems fair. Could you open an issue on
> https://issues.apache.org/jira/projects/CAMEL/issues please?
>
> @sebastian.steinfeld@covestro.com<ma...@covestro.com>
> I added you in cc as you are the author of the commits which added back the
> camel-milo component few months and you might better understand the
> mentioned use and what could be the best to handle it in Camel.
>
> regards,
> ________________________________
> From: Xavier Gagnon <xg...@cogiscan.com>
> Sent: Thursday, May 21, 2026 9:46 PM
> To: users@camel.apache.org <us...@camel.apache.org>
> Subject: [EXTERNAL] camel-milo - Support Custom DataTypes
>
> Hello everyone,
>
> The camel-milo OPC UA Client works well to read and write built-in OPC UA
> DataTypes, but it doesn't seem to work with custom ones. The client is able
> to read the value from a node with a custom DataType and return it as an
> ExtensionObject, but we can't actually decode it without having access to
> the internal milo OpcUaClient's EncodingContexts (and we can't also encode
> it when trying to write the value).
>
> I don't know if the camel client should be the one doing the
> decoding/encoding of custom DataTypes. It might be difficult or even
> impossible for it to correctly determine which EncodingContext to use for
> encoding/decoding values. But if the milo OpcUaClient could be accessed
> from outside the internal Camel classes, the user could get its
> EncodingContexts and do it themselves.
>
> Is it possible to expose the milo OpcUaClient object or its
> staticEncodingContext and dynamicEncodingContext fields?
>
> Best Regards,
> Xavier
> The contents of this email and any attachments are confidential. They are
> intended for the named recipient(s) only. If you have received this email
> by mistake, please notify the sender immediately and do not disclose the
> contents to anyone or make copies thereof. | Le contenu de ce courriel et
> de toute pièce jointe est confidentiel. Ils sont destinés uniquement au(x)
> destinataire(s) nommé(s). Si vous avez reçu ce courriel par erreur,
> veuillez en informer immédiatement l'expéditeur et ne pas en divulguer le
> contenu à quiconque, ni en faire des copies.
>
> Unless otherwise stated above:
>
> Compagnie IBM France
> Siège Social : 17, avenue de l'Europe, 92275 Bois-Colombes Cedex
> RCS Nanterre 552 118 465
> Forme Sociale : S.A.S.
> Capital Social : 664 614 175,50 €
> SIRET : 552 118 465 03644 - Code NAF 6203Z
>
Re: camel-milo - Support Custom DataTypes
Posted by Aurelien Pupier via users <us...@camel.apache.org>.
Hello,
I'm not very familiar with the internals of the Milo component but this request seems fair. Could you open an issue on https://issues.apache.org/jira/projects/CAMEL/issues please?
@sebastian.steinfeld@covestro.com<ma...@covestro.com> I added you in cc as you are the author of the commits which added back the camel-milo component few months and you might better understand the mentioned use and what could be the best to handle it in Camel.
regards,
________________________________
From: Xavier Gagnon <xg...@cogiscan.com>
Sent: Thursday, May 21, 2026 9:46 PM
To: users@camel.apache.org <us...@camel.apache.org>
Subject: [EXTERNAL] camel-milo - Support Custom DataTypes
Hello everyone,
The camel-milo OPC UA Client works well to read and write built-in OPC UA DataTypes, but it doesn't seem to work with custom ones. The client is able to read the value from a node with a custom DataType and return it as an ExtensionObject, but we can't actually decode it without having access to the internal milo OpcUaClient's EncodingContexts (and we can't also encode it when trying to write the value).
I don't know if the camel client should be the one doing the decoding/encoding of custom DataTypes. It might be difficult or even impossible for it to correctly determine which EncodingContext to use for encoding/decoding values. But if the milo OpcUaClient could be accessed from outside the internal Camel classes, the user could get its EncodingContexts and do it themselves.
Is it possible to expose the milo OpcUaClient object or its staticEncodingContext and dynamicEncodingContext fields?
Best Regards,
Xavier
The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email by mistake, please notify the sender immediately and do not disclose the contents to anyone or make copies thereof. | Le contenu de ce courriel et de toute pièce jointe est confidentiel. Ils sont destinés uniquement au(x) destinataire(s) nommé(s). Si vous avez reçu ce courriel par erreur, veuillez en informer immédiatement l'expéditeur et ne pas en divulguer le contenu à quiconque, ni en faire des copies.
Unless otherwise stated above:
Compagnie IBM France
Siège Social : 17, avenue de l'Europe, 92275 Bois-Colombes Cedex
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 664 614 175,50 €
SIRET : 552 118 465 03644 - Code NAF 6203Z