Croway opened a new pull request, #206:
URL: https://github.com/apache/camel-spring-boot-examples/pull/206
## Summary
- `CamelRouter` in the `rest-cxf` example dispatched on
`${header.operationName}`, a header that CXF-RS never sets.
`DefaultCxfRsBinding` actually populates `CamelCxfOperationName` for every
cxfrs request regardless of binding style, so the header resolved empty and
every GET/PUT hit `bean:userServiceImpl?method=` with a blank method name,
throwing `MethodNotFoundException` (500). Only the bean-validation error path
worked, since it short-circuits before the dynamic dispatch. This is a
pre-existing bug, not a regression from any recent bump.
- Fixed by routing on `${header.CamelCxfOperationName}`, matching what the
sibling `soap-cxf` example already does correctly.
- Kept `toD` (rather than switching to `recipientList`) since there is
exactly one computed destination per exchange here — `toD` is the EIP built for
that case, whereas `recipientList` is designed for multicasting to potentially
several recipients.
## Test plan
- [x] `mvn -pl rest-cxf -am package`
- [x] Ran the app (`mvn spring-boot:run`) and exercised all documented
endpoints:
- `GET /services/api/user` → 200, list of users
- `GET /services/api/user/1` → 200, single user
- `PUT /services/api/user` (valid payload) → 201
- `PUT /services/api/user` (invalid payload) → 400 with validation message
(already worked before, still works)
🤖 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]
