This content has been marked as final.
Show 3 replies
-
1. Re: Component references of Bean vs Camel
trohovsky Dec 3, 2014 5:09 AM (in response to ozkin)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
-
2. Re: Component references of Bean vs Camel
ozkin Dec 3, 2014 2:05 PM (in response to trohovsky)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).
-
3. Re: Component references of Bean vs Camel
jorgemoralespou_2 Dec 3, 2014 3:18 PM (in response to ozkin)1 of 1 people found this helpfulWhen 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.