Win a copy of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

JCA Architecture  RSS feed

 
Sunit Mukherjee
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Most implementations have some kind of middleware writing custome interfaces so that J2EE applications talk to legacy/other systems. how does the connector architecture better that?
 
Atul Apte
Author
Greenhorn
Posts: 29
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Sunit,
I am a little bit confused as to what type of middleware are you referring to. I think you mean custom or propriatary middleware that the legacy application is based on. For example the legacy application may be using MQSeries or other messaging platform to interact with the outside world.
In such cases JCA will enable the J2EE applications to communicate with the middleware and send/receive appropriate application messages.
If you are talking about middleware on the J2EE server like a JMS implementation that is not used by the legacy system then JCA really doesnot interface with the JMS implementation unless it provides access to a legacy system.
I hope I understood your question correctly. Think of JDBC as middleware and a JCA adapter for an accounting package that is based on ODBC, will interface with the JDBC driver. That way the J2EE application doesnot realize that the JCA adapter is actually using JDBC to access the legacy system.
Atul
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!