Thanks Tomas. Somehow I missed it from the documentation.....
Could you or someone else explain the purpose of ESB contact types, when one decides to use it? (for example, comparing with Java).
1 of 1 people found this helpful
When you have a contract that can be defined in an interface with one single method, as it does not require an actual class/interface on the filesystem, it is a virtual interface definition. So if you are using a Camel component, or any composite service/reference, you can use ESB type of interface and avoid having a file in the filesystem.