JAXB SOAP Client and Mock Endpoint: Default Namespace Inheritance Across Metro and MOXy

Direct Answer

When the transport layer is redirected to a mock HTTP endpoint without altering JAXB binding code, any divergence between Metro and MOXy should first be treated as a fixture serialization and namespace-URI mismatch—not as a documented JAXB specification gap or a supported provider-specific namespace-inheritance feature. The mock must reproduce the exact namespace structure of the production WSDL, because the client’s mappings are keyed to namespace URIs that the real service would emit.

Confirmed Namespace Rule

XML namespace scoping is deterministic: a default xmlns declaration is inherited by descendant elements only while it is in scope. If the mock omits it, descendants are in no namespace. JAXB mappings keyed to a namespace URI do not receive an implicit ancestor namespace. The XML infoset for identical response bytes is identical across parsers; therefore Metro and MOXy should observe the same namespace URIs and local names for the same fixture.

Likely Explanation

Metro and MOXy may differ in leniency, provider wiring, SOAP-version handling, schema validation, or handling of unexpected namespaces, but these are implementation or configuration artifacts—not a specification gap. Behavior is version- and configuration-sensitive; avoid generalizing from a single fixture.

Fixture Strategy

Mirror production namespace structure, not prefixes:

• Same SOAP envelope namespace (SOAP 1.1 vs 1.2 matters before JAXB runs).
• Same default xmlns declarations on the same ancestors.
• Same elementFormDefault qualification as the XSD.
• Same namespace URIs; ns1 versus a default prefix is irrelevant if URIs match.

Do not configure the client to tolerate missing declarations as the primary fix; that hides contract mismatches. Use normalization only as a temporary diagnostic or when the production contract truly permits optional qualification.

Verification Steps

1. Parse the mock and a known-good response with a namespace-aware parser; print each SOAP body child's namespace URI, local name, and prefix.
2. Diff in-scope namespace declarations at the first failing element, including ancestor default xmlns.
3. Run the same fixture through both JAXB providers to isolate provider-specific leniency.
4. Marshal the fixture locally with the same package-level namespace and elementFormDefault settings as the client, then unmarshal without HTTP.
5. If schema validation is available, validate the mock body against the production XSD before unmarshalling.

Missing Diagnostic

To choose the correct fix, determine whether the failing child element is unprefixed with no default xmlns in scope, or prefixed with a namespace URI different from the mapped namespace. The first requires restoring the declaration; the second requires correcting the URI.