-
Notifications
You must be signed in to change notification settings - Fork 23
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
HL7v2 path information should be used when generating NAKs after failed message validation #53
Labels
Comments
This issue is related to #31. |
Should the path tracking have been implemented in HAPI instead of IPF?.. |
alexandruti
pushed a commit
to alexandruti/ipf
that referenced
this issue
Apr 1, 2020
alexandruti
pushed a commit
to alexandruti/ipf
that referenced
this issue
Apr 1, 2020
alexandruti
pushed a commit
to alexandruti/ipf
that referenced
this issue
Apr 1, 2020
alexandruti
pushed a commit
to alexandruti/ipf
that referenced
this issue
Apr 1, 2020
alexandruti
pushed a commit
to alexandruti/ipf
that referenced
this issue
Apr 1, 2020
alexandruti
pushed a commit
to alexandruti/ipf
that referenced
this issue
Apr 1, 2020
krasserm#64: dynamic route extensions will now fail early if the route fails to startup krasserm#53: alternative way of mllp-dispatch configuration krasserm#65: expose custom 'mllp' component where HL7v2TransactionConfig and AuditStrategies can be set via parameters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The IPF's HL7v2 DSL is now able to track path information. This data should be used to fill the "location" field of the Hl7v2Exception when a such exception is thrown (e. g. after failed message validation).
The text was updated successfully, but these errors were encountered: