Build-time generator that turns a WSDL into a REST/JSON gateway in Go.
Given a WSDL, it generates a typed SOAP client (via
github.com/enuan/soap-go, the enuan hard
fork of way-platform/soap-go) and a Huma-based
REST layer wired with the enuan building blocks (web-go, gonfoo,
m3-go/log), including OpenAPI, configuration scaffolding and tests.
- Architecture, scope and roadmap: PLAN.md
- Status: F4 completed — full
genpipeline (ingest → diagnose → client → model → Huma emit → verify) with session auth, application-state mapping, generated REST/marshal assertions, structural verification and a real pilot (uvetgbt-soap-go: ChatService gateway, smoke-tested against a fake SOAP backend). Next (optional): upstream PRs, richer OpenAPI docs, new services.
go install github.com/enuan/enuan-soap-gen/cmd/enuan-soap-gen@latest# Diagnose a WSDL (no output written).
enuan-soap-gen diagnose -i wsdl/chat.wsdl --fail-on error
# Generate client + gateway in the current module.
cat > soapgen.yaml <<'YAML'
service: chat
wsdl: wsdl/chat.wsdl
module: github.com/enuan/chat-gateway
YAML
enuan-soap-gen gen --config soapgen.yamlgen runs: ingest → diagnose (fails on error findings) → soap gen --client → model extraction → emission → go mod tidy → verify. Flags:
--client-only, --skip-client, --no-tidy, --run-tests.
Standalone verification of an already generated project:
enuan-soap-gen verify --config soapgen.yaml # structural checks
enuan-soap-gen verify --config soapgen.yaml --run-tests # + generated tests
enuan-soap-gen verify --config soapgen.yaml --json # machine readable| Path | Content |
|---|---|
internal/soap/<service>/ |
soap-go client (types + methods) |
internal/api/operations_gen.go |
DTOs, bidirectional converters, huma.Register per operation, mapSOAPError |
internal/api/hooks.go |
written once, never overwritten: SessionProvider, StateMapper |
internal/api/auth_gen.go |
lazy login with cached token (auth.strategy=login) |
internal/api/operations_gen_test.go |
marshal assertions, handler round-trip, REST request per operation (humagin + JSON), OpenAPI document, login, token injection and state-error tests |
internal/config/config_gen.go |
confoo configuration (WSDL endpoint as default) |
cmd/<gateway>/main.go |
web-go + humagin server, m3-go/log |
Makefile, go.mod |
pinned runtime stack, gen/verify targets |
Every operation becomes POST /api/<camelCaseOperation> (configurable through
operations.http); SOAP faults map to 502, timeouts to 504.
Request bodies are capped by max_body_bytes (see below). Without the knob,
Huma's own default applies: 1 MiB, which is too small for gateways that
forward payloads carrying e-mail HTML or attachments (the UVET GBT ChatService
gateway sets 16 MiB). The limit is a generation-time knob because Huma exposes
it per operation, not globally; verify fails if a configured limit is missing
from any huma.Register.
service: rtws
wsdl: wsdl/rtservice.wsdl
module: github.com/enuan/infocar-rtws-go
base_path: /api
max_body_bytes: 16777216 # request body limit per operation; unset = Huma's 1 MiB, -1 = unlimited
soap_bin: "" # empty: go run github.com/enuan/soap-go/cmd/soap
operations:
include: [Login, GetVersion] # empty = all
http:
default: { method: POST, path: "/{operation}" }
auth:
strategy: login # none | login | header (wired in F3)
error_map:
state: # application state inside HTTP 200 (F3)
success_field: Successo
naming:
json: camel # camel | preservemake ci # build + vet + test
make golden # refresh diagnose/emit golden files
make testdata-regen SOAP_BIN=... # refresh testdata/clients fixtures (needs soap CLI)
make e2e SOAP_BIN=... # end-to-end: needs the soap CLI, the network
# and read access to the private enuan modulesCI runs make ci only: the end-to-end tests generate a project that imports
the private enuan stack (m3-go, gonfoo, web-go), so they are local-only.
Test strategy:
testdata/corpus/: anonymized public WSDLs (see its README for the policy);testdata/clients/: committed soap-go clients, so model/emit tests run without the CLI;SOAPGEN_E2E=1regenerates and diffs them;testdata/golden/: deterministic expectations for diagnose reports and the generatedoperations_gen.go.