此内容没有您所选择的语言版本。
3.3. Routing
Table 3.3, “Routing Issues Resolved in 6.1.1” lists the issues resolved in version 6.1.1.
| Issue | Description |
|---|---|
| CAMEL-7141 | Custom HeaderFilterStrategy does not work when set it on either component or endpoint uri |
| CAMEL-7338 | CxfClientCallback should not populate camel exchange OUT message if no response comes back to cxf producer and camel exchange pattern is InOnly |
| CAMEL-7347 | camel-netty - Should return 404 instead of 503 if context-path did not match a route |
| CAMEL-7391 | camel-netty - NettyProduce should use timer from component instead of creating new timer per producer |
| CAMEL-7398 | Salesforce recently changed their login API to use new OAuth fields, which breaks the camel-salesforce component |
| CAMEL-7399 | Camel Salesforce integration tests fail with ClassNotFoundException |
| CAMEL-7423 | Netty HTTP producer ignores requestTimeout option |
| CAMEL-7426 | camel-http component should skip reading the form body if it is bridgeEndpoint |
| CAMEL-7427 | camel-netty-http component should skip reading the form body if it is bridgeEndpoint |
| CAMEL-7456 | Camel PropertiesComponent ignores custom parser in Blueprint |
| CAMEL-7462 | camel-netty-http doesn't use "Expect: 100-continue" correctly |
| CAMEL-7472 | camel-netty - SingleUDPNettyServerBootstrapFactory should wait synchronously for the outcome of joining a UDP multicast group so that we know if the attempt was successful or not |
| CAMEL-7506 | [NettyHttp] Remove headerFilterStrategy option after resolving |
| CAMEL-7545 | Having multiple camelContext in same blueprint bundle may only register the 1st in the OSGi service registry |
| CAMEL-7546 | Avoid clash of CamelContext managementName in OSGi |
| CAMEL-7593 | camel-netty-http consumer uses a fixed 1mb chunked frame size |
| CAMEL-7642 | Netty consumer should return error on invalid request |
| CAMEL-7714 | AdviceWith - Does not honor autoStartup option |
| CAMEL-7736 | Failure to create producer during routing slip or similar eip causes exchange causes error handler not to react properly |
| CAMEL-7885 | Timer - Restarting a timer endpoint may not trigger at expected time the first time |
| CAMEL-7920 | Refresh of the camel-jaxb bundle results a strange behaviour |
| ENTESB-1326 | notices generation doesn't work for Maven 3.1.1 |
| MR-833 | Make Log component and EIP compatible with log4j MDC Sift Appender |
| MR-855 | Netty HTTP consumer doesn't handle "Expect: 100-continue" header |
| MR-893 | [Netty HTTP] Slash appended after parameters |