-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reconsider HL7 charset handling #57
Comments
deferred to a later release |
ohr
pushed a commit
that referenced
this issue
Nov 10, 2021
…essage is marshalled/unmarshalled in addition to static charset configuration
ohr
pushed a commit
that referenced
this issue
Dec 6, 2021
…essage is marshalled/unmarshalled in addition to static charset configuration
ohr
pushed a commit
that referenced
this issue
Dec 22, 2021
…essage is marshalled/unmarshalled in addition to static charset configuration
ohr
pushed a commit
that referenced
this issue
Jan 28, 2022
…essage is marshalled/unmarshalled in addition to static charset configuration
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As of Camel 2.14.1, the HL7MllpDecoder is capable of producing/consuming plain byte arrays and leave string conversion (respecting charsets) to the HL7DataFormat.
In this Camel version, the HL7DataFormat is aware of MSH-18 as well is using a configured charset.
IPF has various HL7-related interceptors and parts that deal with charsets as well. We might want to adapt this and take advantage of this new feature.
The text was updated successfully, but these errors were encountered: