当您要将同一消息发送到多个端点，并且在进入收件人列表之前知道这些端点是什么时，收件人列表是理想的选择。
动态路由器可以将消息路由到许多端点，在输入路由器时不一定知道这些端点的列表和顺序。由于您有一对多的情况，动态路由器可能更适合。
一个可能有效的简单方法是准备一个元组列表。每个元组将包含一个CustomerConfig和一个RemappedMessage。然后，您将split列表，并在拆分器中将消息发送到代理。对于元组，您可以使用ImmutablePair、Map或仅两个元素List。
至于设置url和用户名/密码，我假设您使用的是Camel的HTTP组件。由于http组件允许这样做，所以最好将这些值作为头提供。可以使用CamelHttpUri头设置URL。HTTP组件通常将消息头作为HTTP头传递，因此您可以通过设置同名的消息头来设置Authorization头等内容。
当然，它也支持从交换和消息中的值设置头。

// assumes the body is a List in which the first element is a CustomerConfig
.setHeader("Authorization", simple("${body[0].authValue}"))

实际上，你可能需要做更多的工作来授权。例如，如果是基本授权，你需要计算你想要使用的值。我会在头文件或属性中设置它，然后引用它如下：

.setHeader("Authorization", simple("${header.basicAuthValue}"))
// or
.setHeader("Authorization", simple("${exchangeProperty.basicAuthValue}"))

最后，路径看起来非常复杂，但每个bean只做一件事。

// main route, split to direct:split root and return aggregated list of EventResponse
from("activemq:queue:" + getQueue())
        // note here unmarshall is manual but also use Jsonb
        .bean(EventUnmarshaller.class) // use class form so that Camel will cache the bean
            .setProperty("skipAck", simple("${body.skipAck}"))
        .bean(SomeFieldValidator.class)
        .bean(ConfigDetailsEnricher.class)
        .split(body(), (oldExchange, newExchange) -> { // reduce each new EventResponse into the result list
            if (oldExchange == null) {
                // the first time we aggregate we only have the new exchange,
                // so we just return it
                return newExchange;
            }
            List<EventResponse> list = oldExchange.getIn().getBody(List.class);
            EventResponse newElement = newExchange.getIn().getBody(EventResponse.class);
            list.add(newElement);
            oldExchange.getIn().setBody(list);
            return oldExchange;
        })
            .to("direct:individual")
        .end() // end split
.to("direct:replyRoute");

// split route, all beans here only deals with one EventSpecificConfig; after all convert to EventResponse
from("direct:individual")
        .filter().method(CriteriaFilter.class)
        .bean(AnotherFieldsTailor.class)
        .bean(RestOperationEnricher.class)
        .choice()
            .when(simple("${body.restOperation.name} != 'DELETE'"))
            .bean(NonDeleteOperationEventFieldsTailor.class)
        .end()
        .bean(HttpMethodEnricher.class)
        .bean(TokenRetriever.class) // call oauth endpoint; as here a cache is used for token so have to use a bean. Set token to EventSpecificConfig
        // inject url into header here; as when reaching "toD()", the body already has change to type Event, not EventSpecificConfig
        .bean(EventApiConfiguration.class) // after this step, body is already new event(PUT, POST) / null(DELETE)
        .choice()
            .when(simple("${body} != null"))
                .marshal().json(JsonLibrary.Jsonb)
            .endChoice()
        .end()
        .toD("${header.url}", 10) // only cache at most 10 urls
        ;

from("direct:replyRoute") // list of EventResponse
        .bean(EventResponsesProcessor.class)
        .log(LoggingLevel.DEBUG, "Reply: " + simple("${body}"))
        .setHeader("from", constant("MYAPP"));

对于API配置：

@Handler
void configure(EventSpecificConfig eventSpecificConfig, Exchange exchange) {
    ConfigDetail configDetail = eventSpecificConfig.getConfigDetail();
    String httpMethodUpperCase = eventSpecificConfig.getHttpMethod().getMethodName();
    SubscriptionEvent newEvent = eventSpecificConfig.getNewEvent();
    Message message = exchange.getIn();
    message.setHeader("Authorization", "Bearer " + eventSpecificConfig.getToken());
    message.setHeader(Exchange.HTTP_METHOD, httpMethodUpperCase);
    message.setHeader(HttpHeaders.CONTENT_TYPE, MediaType.APPLICATION_JSON);
    if (HTTP_METHODS_WITH_PATH.contains(httpMethodUpperCase)) {
        message.setHeader(Exchange.HTTP_PATH, "/" + newEvent.getImsi());
    }
    if (HTTP_METHODS_WITH_BODY.contains(httpMethodUpperCase)) {
        message.setHeader(HttpHeaders.CONTENT_TYPE, MediaType.APPLICATION_JSON);
        message.setBody(newEvent);
    } else { // DELETE
        message.setBody(null); // DELETE has no body
        // more logic of setting headers for HTTP query params depending on config values
    }
    message.setHeader("url", configDetail.url()); // toD() has no access to EventSpecificConfig, only header works
}

我发现choice().when().endchoice().otherwise().endchoice().end()在每个分支中都需要一个to()，而我不能使用when().setHeader().endchoice()，所以最后我决定将所有这些逻辑放到一个bean中。
并且必须使用end()来结束choice()，不能使用endchoice(); endchoice()是针对when()和otherwise()的。相当误导。

choice()
    .when(simple("${header.foo} == 'bar'"))
        .to("x")
    .endchoice()
    .otherwise()
        .to("y")
    .endchoice()
.end()

型
我以为endchoice()和choice()是一个级别的，为什么不叫endbranch()呢？