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

   ## Problem
   
   All 8 of the component's non-primitive header `javaType` values name their 
class by simple name only:
   
   ```java
   @Metadata(label = "producer", description = "An optional timeout applied to 
the operation.", javaType = "Duration")
   public static final String TIMEOUT = HEADER_PREFIX + "Timeout";
   ```
   
   ```json
   "CamelAzureStorageQueueTimeout": { ..., "javaType": "Duration", ... }
   ```
   
   Fully qualified is the convention by a wide margin - across the whole 
catalog, 3692 header `javaType` values are fully qualified or a built-in type, 
and 151 are not.
   
   `Duration` and `OffsetDateTime` are `java.time`, and `QueuesSegmentOptions` 
is `com.azure.storage.queue.models` - none of which the simple name says. The 
sibling `camel-azure-storage-blob` and `camel-azure-storage-datalake` have the 
same gap, so a reader comparing the three queue/blob/datalake header tables 
sees no type they can resolve.
   
   ## Fix
   
   Qualify all 8, taking each FQN from the import the module itself uses. 
Header names are untouched.
   
   Metadata only - no behaviour change. I diffed the regenerated catalog file 
against `main` and confirmed the 8 `javaType` values 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