Open
Conversation
… misc UI & spider fixes Implement DOM-based XML body generation in BodyGenerator Add BodyGenerator.generateXml(MediaType) and generateXml(Schema) Prefer media-type examples; otherwise generate XML from Schema Support common xml.* metadata: xml.name, xml.attribute, xml.wrapped, xml.namespace and xml.prefix Handle primitives, arrays (wrapped / unwrapped), object properties, additionalProperties (serialized as <entry><key/><value/>), BinarySchema placeholder, and basic composed-schema handling (oneOf/anyOf/allOf merge) Emit generator error messages on failures (preserve existing error collection) Wire XML generation into request conversion RequestModelConverter: detect application/xml, text/xml and application/*+xml, prefer exact application/xml and call BodyGenerator.generateXml(...) instead of logging unsupported-content Tests and integration Add/tighten unit tests in BodyGeneratorXmlUnitTest that parse generated XML and assert structure (elements, attributes, namespaces, counts) Update v3 BodyGeneratorUnitTest where necessary Add integration test OpenApiIntegrationXmlTest and test resource openapi_xml_integration.yaml to verify generated XML bodies and removal of the previous unsupported-content message Miscellaneous improvements / cleanup ImportDialog: minor formatting, switch validation to use java.net.URI to avoid deprecated URL-based parsing and avoid deprecated constructors SpiderDialog & UrlCanonicalizer: minor whitespace/formatting fixes and replace deprecated URL(String,...) usage with URI construction where appropriate (avoid deprecated constructors) Small refactors and formatting adjustments across changed files
…fail for complex or invalid schemas
…napi/resources/help/contents/openapi.html Co-authored-by: Rick M <kingthorin@users.noreply.github.com> Signed-off-by: W0lfbane <3799912+W0lfbane@users.noreply.github.com>
Member
|
Great job! No new security vulnerabilities introduced in this pull requestUse @Checkmarx to reach out to us for assistance. Just send a PR comment with Examples: |
Signed-off-by: W0lfbane <3799912+W0lfbane@users.noreply.github.com>
Signed-off-by: W0lfbane <3799912+W0lfbane@users.noreply.github.com>
Author
|
Happy new year! Just wanted to follow-up with this, is this on the roadmap to be reviewed any time this quarter? |
Member
|
Yes. |
thc202
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Recreating PR #6793 — the original was closed unintentionally when my fork was archived. Original PR: #6793