davsclaus opened a new pull request, #117:
URL: https://github.com/apache/camel-jbang-examples/pull/117

   CAMEL-25764: the route rung does not show dynamic routing, failover or 
throttling yet. This adds them in one example, with the web shop orders.
   
   ## What
   
   - **`route/dynamic-routing`:**
     - **`recipientList`** computes the endpoints from each order with Simple: 
`direct:warehouse-${body[country]},direct:billing-${body[status]}`, with a 
route for each endpoint. The pending ORD-1003 goes to `billing-pending` and 
gets no invoice. Simple has no ternary, so encoding the status in the endpoint 
name is the readable way to make billing depend on it.
     - **`loadBalance` with `failoverLoadBalancer`:** the primary invoice 
service is down (`throwException`, with `noErrorHandler` on its route), and the 
backup takes over. `inheritErrorHandler: false` makes it fail over at once. 
Without it, the route's error handler logs an ERROR "Failed delivery" for every 
expected failover.
     - **`throttle`:** the US warehouse takes at most one order per second.
   - **README** with the usual sections, and a **Citrus YAML test** in the CI 
matrix. It is sixth in the route group.
   
   ## Checks
   
   - `camel validate yaml --canonical` reports nothing.
   - The routes run on the released Camel 4.23.0 with no errors in the log.
   - The Citrus test passes (TEST SUCCESS).
   
   ## Merge note
   
   apache/camel-jbang-examples#116 (route/enrich-and-dedupe, fifth in the 
group) is open too. Whichever of the two merges second needs a rebase: 
`./generate-catalog.sh`, plus one line in `build.yml`.
   
   _Claude Code on behalf of davsclaus_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   
   https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m
   


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