Skip to content

Conversation

@W0lfbane
Copy link

@W0lfbane W0lfbane commented Nov 8, 2025

Recreating PR #6793 — the original was closed unintentionally when my fork was archived. Original PR: #6793

W0lfbane and others added 6 commits November 5, 2025 10:44
… 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
…napi/resources/help/contents/openapi.html

Co-authored-by: Rick M <[email protected]>
Signed-off-by: W0lfbane <[email protected]>
@psiinon
Copy link
Member

psiinon commented Nov 8, 2025

Logo
Checkmarx One – Scan Summary & Details87b6833a-ee2a-413b-a4a1-e7600d7cca21

Great job! No new security vulnerabilities introduced in this pull request


Use @Checkmarx to reach out to us for assistance.

Just send a PR comment with @Checkmarx followed by a natural language request.

Examples: @Checkmarx how are you able to help me? @Checkmarx rescan this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants