This week's book giveaways are in the Java EE and JavaScript forums.
We're giving away four copies each of The Java EE 7 Tutorial Volume 1 or Volume 2(winners choice) and jQuery UI in Action and have the authors on-line!
See this thread and this one for details.
The moose likes Websphere and the fly likes RMI vs. SOAP for EJB calls from client application Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "RMI vs. SOAP for EJB calls from client application" Watch "RMI vs. SOAP for EJB calls from client application" New topic
Author

RMI vs. SOAP for EJB calls from client application

Scott DiNucci
Greenhorn

Joined: Aug 16, 2002
Posts: 2
I am working on a project to add additional functionality to an existing client-side Java application. The client was built using RMI to call EJBs. The new functionality will be built using WSAD 4.0.3 and deployed on a WAS 4.0.1 server. We are being asked to look at using SOAP instead of RMI. Using SOAP, can the client application call the EJBs or will a servlet need to be written? The reason I ask is the EJBs are written to the 1.1 specification since WAS 4.0.x does not support the 2.0 specification. Will we use JAXM or JAX RPC? Are these supported by the version of WSAD and WAS we are using. Does SOAP provide a clear reason for moving away from RMI? If anyone can point me to a good source of information or example as it relates to our environment, it would be appreciated.
 
Don't get me started about those stupid light bulbs.
 
subject: RMI vs. SOAP for EJB calls from client application