Dhairya-007 opened a new pull request, #30105:
URL: https://github.com/apache/camel/pull/30105
## Problem
camel-azure-eventgrid publishes a header `javaType` that names its class by
simple name only:
```
CamelAzureEventGridEventTime OffsetDateTime
```
`OffsetDateTime` is `java.time.OffsetDateTime`. The sibling Azure components
document the same type on their timestamp headers, so spelling it out keeps the
Azure family consistent.
Fully qualified is the convention by a wide margin across the catalog: 3692
header `javaType` values are fully qualified or a built-in type, and 151 are
not.
## Fix
Qualify it, taking the FQN from the import the component's own sources use:
```
CamelAzureEventGridEventTime OffsetDateTime
-> java.time.OffsetDateTime
```
Container spellings (`List`, `Collection`, `Map`) keep their bare form,
matching the rest of the catalog, and header names are untouched.
Metadata only - no behaviour change. I diffed the regenerated catalog file
against `main` and confirmed the listed `javaType` value(s) are the only fields
that differ.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]