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

   ## Problem
   
   The operation header names its enum by simple name only:
   
   ```java
   @Metadata(description = "The operation to perform", javaType = 
"DoclingOperations")
   public static final String OPERATION = "CamelDoclingOperation";
   ```
   
   `DoclingOperations` is 
`org.apache.camel.component.docling.DoclingOperations`.
   
   Because the short name does not resolve, the header loses its value list: 
the generator derives an `enum` from a resolved enum class, so the catalog 
published no accepted values for the one header that decides what the producer 
does.
   
   ```json
   "CamelDoclingOperation": { ..., "javaType": "DoclingOperations", ..., 
"description": "The operation to perform" }
   ```
   
   The matching `operation` URI option has always listed all 15, because its 
field is typed. After qualifying the header's `javaType` the two agree:
   
   ```
   operation option : 15 values
   operation header : 15 values   (was none)
   ```
   
   That gap matters here more than most: operation names like 
`BATCH_EXTRACT_STRUCTURED_DATA`, `SUBMIT_ASYNC_CONVERSION` and 
`CHUNK_HIERARCHICAL` are not guessable, and the header is the only way to vary 
the operation per exchange.
   
   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 to `org.apache.camel.component.docling.DoclingOperations`, the 
FQN the component's own sources import. The header name is untouched.
   
   Metadata only - no behaviour change. I diffed the regenerated catalog file 
against `main`: the only differences are this `javaType` and the `enum` list 
appearing beside it.
   


-- 
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