Skip to content
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

[BUG] Strict Parser adding namespace in the wrong spot #5722

Closed
mefrehner opened this issue Mar 15, 2023 · 0 comments
Closed

[BUG] Strict Parser adding namespace in the wrong spot #5722

mefrehner opened this issue Mar 15, 2023 · 0 comments
Labels
bug Something isn't working Fix-Commited Issue fixed and will be available in milestone Internal-Issue-Created An issue has been created in NextGen's internal issue tracker RS-9886 triaged
Milestone

Comments

@mefrehner
Copy link
Collaborator

Describe the bug
The Strict Parser is adding the namespace in the wrong spot of the XML header making the header not end with “?>” making it invalid.

To Reproduce
Setup steps (if required). Example:

  1. Install Mirth Connect version 4.2.0
  2. Create a Channel
  3. Set all data types to HL7 v2.x and turn check "Use Strict Parser" for the inbound and outbound properties.
  4. Create an XSLT transformer step and set msg equal to the XML generated by the XSLT transformer step

Steps to reproduce the behavior:

  1. Send an HL7 message into the channel
  2. Check the error

Expected behavior
The Strict Parser adds the namespace to the XML header, and makes sure that it ends with “?>”

Actual behavior
The Strict Parser adds the namespace to the XML header, but the header does not end with “?>” making it invalid.

Workaround(s)
Are there one or more workarounds for this issue currently?

@mefrehner mefrehner added bug Something isn't working triaged Fix-Commited Issue fixed and will be available in milestone Internal-Issue-Created An issue has been created in NextGen's internal issue tracker RS-9886 labels Mar 15, 2023
@mefrehner mefrehner added this to the 4.3.0 milestone Mar 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Fix-Commited Issue fixed and will be available in milestone Internal-Issue-Created An issue has been created in NextGen's internal issue tracker RS-9886 triaged
Projects
None yet
Development

No branches or pull requests

2 participants