k-krawczyk commented on PR #30256:
URL: https://github.com/apache/camel/pull/30256#issuecomment-6941419998

   Thanks, all three cases are real and the fix is in c813714.
   
   **A value whose text is its toString().** `UUID`, `URI`, `URL`, `Temporal`, 
`TemporalAmount` and `Date` are now read as text. Your diagnosis holds: the 
only `UriTypeConverter` in core converts a String to a URI, not back, and there 
is nothing at all for `UUID`, so a `UUID` job id for `textExtractionFetch` did 
fail. This stays a short list of value types rather than a list of text 
carriers, so it does not bring back what CAMEL-26553 reports.
   
   **JsonNode and a custom converter that returns toString().** These two 
cannot be told apart from a POJO without guessing, so instead of guessing the 
error message now offers a way out: `convertBodyTo(String.class)` when the 
`toString()` of the object is the text to send. The body is then a String, 
which is a payload, and it goes through. The rule itself is also stated in the 
component page and the upgrade guide, so both of the options you offered are in.
   
   **The docs paragraph.** Moved out from between the operations sentence and 
its list into its own `=== Message body read as text` section.
   
   **The path and id reads.** @oscerd approved the PR with those nine reads 
already in the diff, so I read that as the confirmation you asked for. Happy to 
drop them if he prefers the narrower scope.
   
   **The unchecked List cast in getInputs.** Filed as its own ticket.
   
   47 tests in the module, green with `-Psourcecheck`. The `license-check` job 
failed on a 403 while the Maven wrapper downloaded 
`apache-maven-3.9.16-bin.zip`, which is unrelated to this change and needs a 
re-run.
   
   _Reported by Claude Code on behalf of Karol Krawczyk_


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