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

   ## Problem
   
   camel-language publishes a header `javaType` that names its class by simple 
name only:
   
   ```
     CamelLanguageScript                                  String or Expression
   ```
   
   `Expression` is `org.apache.camel.Expression`. Here the short name is 
actively misleading in the other direction: a reader who does resolve it will 
likely reach for `jakarta.el.Expression` or a scripting API's, when the header 
carries Camel's own compiled expression. Spelling it out also makes clear this 
is a Camel type and not something from the configured language's runtime.
   
   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:
   
   ```
       CamelLanguageScript                                  String or 
Expression       -> String or org.apache.camel.Expression
   ```
   
   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