gnodet commented on code in PR #23184:
URL: https://github.com/apache/camel/pull/23184#discussion_r3232776909
##########
core/camel-api/src/generated/java/org/apache/camel/ExchangeConstantProvider.java:
##########
@@ -168,7 +166,7 @@ public class ExchangeConstantProvider {
MAP = map;
}
- public static @Nullable String lookup(String key) {
+ public static String lookup(String key) {
Review Comment:
_Claude Code on behalf of Guillaume Nodet_
Good catch — this was a spurious change from the build regenerating
`ExchangeConstantProvider.java` without the `@Nullable` annotation. Reverted in
the latest push.
##########
core/camel-api/src/main/java/org/apache/camel/ProducerTemplate.java:
##########
@@ -45,9 +45,7 @@
* <ul>
* <li>throws {@link org.apache.camel.CamelExecutionException} if processing
failed <i>during</i> routing with the
* caused exception wrapped</li>
- * <li>The <tt>fault.body</tt> if there is a fault message set and its not
<tt>null</tt></li>
- * <li>Either <tt>IN</tt> or <tt>OUT</tt> body according to the message
exchange pattern. If the pattern is Out capable
- * then the <tt>OUT</tt> body is returned, otherwise <tt>IN</tt>.
+ * <li>The <tt>OUT</tt> body if the pattern is Out capable, otherwise
<tt>IN</tt>.
Review Comment:
_Claude Code on behalf of Guillaume Nodet_
The `fault.body` concept (fault messages) was removed in Camel 3.0 — there
is no `setFault`/`isFault` on `Message` anymore in the current API. This
Javadoc was left over from Camel 2.x and no longer describes actual behavior,
so keeping it was misleading.
--
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]
