Skip to content

Make ceSource accessible to calling application - #121

Open
jodelkreismeister wants to merge 4 commits into
cap-java:mainfrom
jodelkreismeister:fix-issue119
Open

jodelkreismeister wants to merge 4 commits into
cap-java:mainfrom
jodelkreismeister:fix-issue119

Conversation

@jodelkreismeister

Copy link
Copy Markdown

No description provided.

sap-andreas-paul and others added 3 commits September 11, 2026 15:19
Introduces KEY_SUBACCOUNT_ID ("btp.subaccountId") so applications can
supply the BTP subaccount ID as the ceSource suffix instead of the
tenant ID — relevant when the two differ (e.g. IAS-based scenarios).

Replaces fillCeSource/putIfAbsent with a direct headers.put: the
framework's cloudEventsFormatter pre-populates KEY_SOURCE before
emitTopicMessage runs, so putIfAbsent was silently a no-op and the
binding-derived ceSource was never applied.

Removes EVENT_HUB_EMIT_INVALID_CE_SOURCE (50007032) which is no longer
needed, and restores ceSource to private visibility.
kevin-b-sap
kevin-b-sap previously approved these changes Sep 21, 2026

@kevin-b-sap kevin-b-sap left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change is sound. I added a section to the readme and changelog.

This branch has not been deployed

No deployments
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.

4 participants