Details
-
Type:
Improvement
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: camel-netty4
-
Labels:None
-
Estimated Complexity:Unknown
Description
Currently you would need to extend camel-netty4 and override NettyProducer where you would override
- getState
- removeState
- putState
methods where you have your own correlation id mapping so you can map the multiplexed requesy/replies to the correct Camel Exchange / AsyncCallback pair.
We can likely add some new SPI interface to camel-netty4 where we can make this easier for 3rd party to plugin their custom logic.