problemXmlContent

Adds application/problem+xml beside whatever this response already documents.

Written inside a problemResponse/problemDefault block, so one response describes both formats:

responses { problemResponse(OutOfCredit) { problemXmlContent() } }

The XML object records RFC 9457 Appendix B's root element and namespace. That namespace is RFC 7807's, unchanged, because the wire format did not change between the two documents.

The schema is retitled with an Xml suffix so that it becomes its own component. Ktor keys components/schemas by title alone and the last schema registered under a title wins, so sharing one with the JSON variant would let whichever route is walked last decide whether the component carries this XML object at all.

Parameters

Samples

routing {
    get("/orders/{id}") {
        call.respondText("an order")
    }.describe {
        responses {
            // One response, both media types: the application negotiates between them.
            problemResponse(OutOfCredit) { problemXmlContent() }
        }
    }
}