Zakaria El OrcheandClaude Opus 5
adcd6376b6
flash-ext-jackson and flash-ext-validation become three modules: - flash-ext-jackson-core: the Codec (one mapper, body/write/writeView), JacksonHandler, the outbound marshalling, and the constraint engine that used to be flash-ext-validation - flash-ext-jackson-json: Json, JsonExtension, JsonHandler - flash-ext-jackson-xml: Xml, XmlExtension, XmlHandler Every Jackson format is the same databind model behind a different factory, so the annotations, the constraints and the published schema are the same for all of them: only the mapper and the content type differ, and that is all a format module says. A route picks its format by the handler it extends — there is no negotiation and nothing to configure. A typed body is now always verified against its own type's jakarta constraints, whatever the format: malformed is a 400, a broken constraint is a 422, and neither reaches the handler. The validator was already allocation-free and stays so; validating is no longer something an application remembers to do. bodyFrom is gone. body has the streaming semantics, because the request's stream is reused per connection while bytes() allocates the whole body: one name, the path that does not allocate. JacksonExtension is JsonExtension, and autoJson() is auto(). The root POM now manages every module of this build, so anything composing Flash imports it once and never names a version again. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
flash-ext-jackson-xml
XML bodies and XML responses, over the same types as every other Jackson format.
XmlExtension xml = new XmlExtension();
app.install(xml).use(xml.auto());
@POST("/orders")
public final class PlaceOrder extends XmlHandler<Order> {
@Inject private OrderService orders;
@Override protected Object handle(Request req, Response res, Order body) {
return orders.place(body);
}
}
Everything flash-ext-jackson-json does, in XML: the body is read off
the request stream, verified against the constraints its type declares, and handed over. A type
annotated for JSON works here as is — Order can be a JSON body on one route and an XML body on
another.
What is specific to XML is Jackson's own: @JacksonXmlRootElement for the root name,
@JacksonXmlProperty(isAttribute = true) for an attribute rather than an element, and
@JacksonXmlElementWrapper for how a list is wrapped. This module adds no annotations of its own.
Brings jackson-dataformat-xml, and with it Woodstox.