0

Popular Enterprise information systems (EIS) provide REST API and JCA to integrate with Java EE web applications. When REST API is avialable, why & when we should go for JCA based integration ?

For example, Salesforce provides excellent REST API(s). Also there are developers who develop JCA connectors for Salesforce, like this. I am unable to justify why I should go for JCA when REST is so flexible & easy to integrate with any application.

Sairam Krish
  • 10,158
  • 3
  • 55
  • 67
  • Why would you think you should, out of interest? JCA is for legacy systems, so I'd be curious to hear the use case where it would be preferable to an easy to use REST service. – Evan Knowles Aug 12 '14 at 05:57
  • Exactly, that's my doubt. When we have REST API exposed for integration, why we should go JCA. Does it provide any promising advantage over REST? – Sairam Krish Aug 12 '14 at 06:07
  • Well, Just for Legacy many not be right. For instance, if you have your own datasource or you want custom handing, then you need to use JCA. – Kevin Rave Aug 14 '14 at 21:28

0 Answers0