Dhairya-007 opened a new pull request, #30101:
URL: https://github.com/apache/camel/pull/30101

   ## Problem
   
   camel-crypto publishes a header `javaType` that names its class by simple 
name only:
   
   ```
     CamelSignaturePublicKeyOrCert                        Certificate or 
PublicKey
   ```
   
   `Certificate` is `java.security.cert.Certificate` and `PublicKey` is 
`java.security.PublicKey` - two different packages, which the bare names hide. 
`Certificate` in particular is ambiguous even within the JDK: 
`java.security.Certificate` exists too (deprecated since 1.2), so the short 
name names a type that is both real and the wrong one.
   
   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:
   
   ```
       CamelSignaturePublicKeyOrCert                        Certificate or 
PublicKey   -> java.security.cert.Certificate or java.security.PublicKey
   ```
   
   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]

Reply via email to