Layer 7 SOAP migration to Gravitee, proven with an equivalence report
A Layer 7 SOAP export can become a running Gravitee API, with a report naming every assertion it would not convert and a request-by-request comparison showing where the new API behaves like the old one
Pre-release buildInternal only
Say while it plays
The converter refuses any assertion it has no mapping for, by name, and then produces no API at all rather than one that is quietly less strict than the old gateway; a person decides each refused item.
The equivalence report sends the same test pack to the old gateway and to Gravitee, only compares requests the old side answered, and marks any operation the pack never called as unverified.
Here 15 of 16 requests matched. The one divergence was a client sending no SOAPAction header: the old gateway worked out the operation from the body and the converter only reads the header, so one request needs fixing by hand.
Don't claim
Don't claim the converter built the REST front end: the recording says it did, but Sam configured that API by hand.
Don't claim credentials map across automatically: the recording says API keys do, but the converter refuses every authentication assertion and a person decides each one.
Don't claim other legacy gateways are supported, or that a whole API failed: only Layer 7 has evidence, and the recording's 'one API' to migrate by hand is one diverging request.