Hi Sanjay, That depends in part on how mission critical is the small application to the integration scenario. The application may be small but if its critical to the scenario then a JCA adapter is still justified in my opinion. You are right in asking the question in terms of the cost involved in developing JCA adapters and their usefulness. I personally prefer to use an adapter framework that can be implemented as a JCA adapter when required or an EJB, or a standalone component, depending on the integration scenario. Also, with more resource adapter vendors the cost of adapters for ERP and other packages should go down. Atul
Atul Apte<br />President and CEO <a href="http://www.iconexio.com/" target="_blank" rel="nofollow">iConexio Technologies Inc</a>.<br />Author of <a href="http://www.amazon.com/exec/obidos/ASIN/0672323109/ref=ase_electricporkchop" target="_blank" rel="nofollow">Java Connector Architecture: Building Enterprise Adaptors</a>
interesting... when it is worth to use JCA in your opinion? maybe either over Web services as XML/SOAP and UDDI? Still not that clear about JCA. Got this from other thead. "Hence web service is not an extension of the application server or any other platform but more of a access mechanism that can be used to invoke functions across the Internet." Wouldn't using Web Service be easier? If want we want to talk over the Web that is. I am still comparing web serviec with JCA!! Don't know why! Maybe you can help. Thanks a lot!!
Joined: Feb 19, 2002
Fei, In my opinion JCA is the way to go when your business case is about a J2EE application requiring to integrate with non-J2EE application. For other scenarios like legacy systems accessing J2EE applications, JCA is not the ideal choice. Message driven beans or web services (for the J2EE application) will be a better choice. Building a JCA adapter for a legacy system only helps a J2EE application get access to the legacy system. What if the legacy system already has a web service? I will still build a JCA adapter to maintain a consistent CCI based interface to the EAI tools. Hope this makes sense. Atul