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

fromJson function provides namespaces and their prefixes in an invalid format #2809

Closed
kalaiyarasiganeshalingam opened this issue Mar 24, 2022 · 2 comments
Assignees
Labels
module/xmldata Points/1 Points/2 Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Team/DIU Data, IO, and Util packages related issues Type/Bug
Milestone

Comments

@kalaiyarasiganeshalingam
Copy link
Contributor

Description:
Namespaces of the XML and its prefixes must combine using colon (:) and other symbols are not valid.

Xml output of fromjson function:

<?xml version="1.0" encoding="UTF-8"?>
<Envelope xmlns_soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns_urn="urn:messages_2020_2.platform.webservices.netsuite.com" xmlns_urn1="urn:core_2020_2.platform.webservices.netsuite.com"></Envelope>

Expected output:

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:messages_2020_2.platform.webservices.netsuite.com" xmlns:urn1="urn:core_2020_2.platform.webservices.netsuite.com"></soapenv:Envelope>
@kalaiyarasiganeshalingam
Copy link
Contributor Author

Closing this issue as this has been fixed by ballerina-platform/module-ballerina-xmldata#418 & added testcase by this.

@github-actions
Copy link

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.

@kalaiyarasiganeshalingam kalaiyarasiganeshalingam added the Reason/EngineeringMistake The issue occurred due to a mistake made in the past. label Apr 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module/xmldata Points/1 Points/2 Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Team/DIU Data, IO, and Util packages related issues Type/Bug
Projects
None yet
Development

No branches or pull requests

1 participant