Skip to content

Remove optional receiverId field if value is not present - #93

Merged
ekarankow merged 3 commits into
epam:mainfrom
YakubenkoIv:fix-receiver-header
Aug 10, 2026
Merged

Remove optional receiverId field if value is not present#93
ekarankow merged 3 commits into
epam:mainfrom
YakubenkoIv:fix-receiver-header

Conversation

@YakubenkoIv

Copy link
Copy Markdown
Contributor

No description provided.

Ivan Yakubenko added 2 commits August 10, 2026 16:44
actions/setup-java@v1 fails to resolve JAVA_HOME on macos-latest runners
since GitHub moved them to Apple Silicon (arm64) - it looks for an x64 JDK
that was never installed there. v4 with an explicit distribution correctly
detects the runner architecture.
…) messages

StructureHeaderXmlBeanBuilder is shared by two schema contexts with different
Receiver cardinality: StructureHeaderType (query/availability responses, where
Receiver is minOccurs="0") and BasicHeaderType via RegistryInterfaceType.Header
(submit/query registry protocol, where Receiver is required, exactly one).

Removing the forced fallback from the shared builder broke the latter
(SchemaValidationException in SubmitStructureResponseBuilderTest). Added
V2_1Helper.ensureReceiverPresent(), called from the two call sites that build
a RegistryInterfaceType header via StructureHeaderXmlBeanBuilder, to patch in
a default Receiver only where the schema actually requires one.
@ekarankow
ekarankow merged commit 00d66fe into epam:main Aug 10, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants