This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes EJB and other Java EE Technologies and the fly likes JCA, JMS or blocking API. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "JCA, JMS or blocking API." Watch "JCA, JMS or blocking API." New topic
Author

JCA, JMS or blocking API.

Tonny Tssagovic
Ranch Hand

Joined: Dec 30, 2003
Posts: 226
What is the best way to connect your J2ee Application to an EIS system that has a CORBA interface by means of asynchronous methods (with call-backs).
1) Just use CORBA from your EJBs, and fork thread out to wait for the callback from the external system and cross your fingers
2) Use an API provided by the system that actually has blocking synchronous calls, but is creating threads itself (same as above from the container�s point of view)
3) Use Common Client Interface JCA
4) Use JMS
And especially WHY? Is JCA hard to learn? Any experience with JCA?
Any thoughts?
Thanks.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: JCA, JMS or blocking API.
 
Similar Threads
Adapter
Legacy Connectivity ....thanx John and Amanda
File Access from EJB running under WebSphere 5.0.2
JCA JMS simple example
Java Connector for Siebel and Websphere App Server