Component references of Bean vs Camel

[ozkin]

Hi, is it so that Bean component can have only Java component references and Camel component can have all three types references (Java, WSDL, ESB) ?

[trohovsky]

Hi Max,

you are right. As the documentation says:

• Java is the only valid interface type for bean services. Bean - SwitchYard - Project Documentation Editor
• Camel supports Java, WSDL, and ESB contract types. Camel - SwitchYard - Project Documentation Editor

Tomas

[ozkin]

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

[jorgemoralespou_2]

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.