From document binding to layer-to-layer mapping to full schema-driven code generation — see how TwinMapper replaces fragmented toolchains with a single compile-time platform.
Bind YAML, JSON, and BPMN XML runtime documents into strongly typed generated DTOs. The NodeCursor abstraction provides format-neutral traversal — generated binders have zero dependency on Jackson, SnakeYAML, or StAX directly.
Replace hand-written deserialization, manual field mapping, and scattered @JsonProperty annotations with a single definition file that drives the entire binding pipeline.
Generate typed Java-to-Java mappers for every architectural boundary: entity↔domain, domain↔DTO, DTO↔entity, entity↔projection, request/command↔domain, and domain↔event/view/response.
Three mapper modes address different lifecycle stages: CREATE builds new targets, UPDATE applies changes with configurable null policy, and PATCH applies only non-null fields.
Write one YAML definition; get DTOs, enums, binders, validators, registries, metadata descriptors, and object mappers. The five-stage pipeline (Validate → Plan → Generate → Customize → Render) is fully deterministic — identical inputs always produce identical outputs.
Replace jsonschema2pojo for DTO generation, eliminate hand-written mapper boilerplate, and unify your binding and mapping toolchain.
Parse BPMN XML process definitions into typed Java models without any process engine dependency. TwinMapper uses JDK StAX directly — no Camunda, no Flowable, no vendor lock-in.
BPMN is treated as an authoring format, not a workflow engine. Definitions are parsed into the canonical meta-model and feed the same code generation pipeline as YAML and JSON.
TwinMapper unifies capabilities that previously required assembling three separate tools. MapStruct handles object mapping; jsonschema2pojo handles DTO generation; Jackson/SnakeYAML handle parsing. TwinMapper provides all three from a single definition source.