davsclaus opened a new pull request, #28422:
URL: https://github.com/apache/camel/pull/28422
_Claude Code on behalf of davsclaus_
A follow-up to the catalog body types of CAMEL-24961 (#28410).
camel-whatsapp receives events in webhook mode (`webhook:whatsapp:...`), but it
was marked producer only, so the catalog could not describe the body the
webhook route gets, and tools that read the catalog treated whatsapp as
producer only.
**Changes**
- `WhatsAppEndpoint` is no longer `producerOnly`. `createConsumer` says "Use
webhook component to wrap this endpoint", as camel-clickup does.
- `WhatsAppEndpoint` extends `DefaultEndpoint` instead of
`ScheduledPollEndpoint`, as it never polls. So the only new consumer options
are `bridgeErrorHandler`, `exceptionHandler` and `exchangePattern`, not the
scheduler options.
- New body types:
- `consumerOut`: the event as JSON text. The GET verification request also
reaches the route, with the `hub.challenge` as the body, or with no body on 403
or 400. With `webhookSecret`, an unsigned event does not reach the route.
- `consumerReply`: not sent; the reply is the body the route got.
- The component description says it receives events in webhook mode. There
is a 4.24 upgrade guide entry.
- The JSON is regenerated and the catalog copy updated, and the Endpoint and
Component DSL are regenerated. `WhatsAppEndpointBuilder` and `whatsapp(path)`
keep their names; the builder now also extends the consumer builder.
**Local checks**
- camel-whatsapp builds and its tests pass, with no drift after the build.
- The catalog copies equal the module; camel-catalog tests: 1105 run, 0
failures.
- camel-yaml-dsl-validator: 295 run, 0 failures.
- camel-jbang-core passes. `ExportTest` needed a fresh camel-kamelet-main
for CAMEL-25186, and then passes: 142 run, 0 failures.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
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]
