Dhairya-007 opened a new pull request, #30099:
URL: https://github.com/apache/camel/pull/30099
## Problem
camel-jcache publishes a header `javaType` that names its class by simple
name only:
```
CamelJCacheEntryProcessor
EntryProcessor<Object, Obj
```
`EntryProcessor` is `javax.cache.processor.EntryProcessor`, from the JSR-107
API rather than from any particular cache provider. Several providers ship a
class of the same simple name (Hazelcast, Infinispan and Ignite among them), so
a reader cannot tell from `EntryProcessor` which interface their object must
implement - and passing a provider's own type where the JSR-107 one is required
is exactly the mistake the bare name invites.
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:
```
CamelJCacheEntryProcessor
EntryProcessor<Object, Obj -> javax.cache.processor.EntryProcessor<Object,
Object, Object>
```
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]