RMI vs. SOAP for EJB calls from client application
Joined: Aug 16, 2002
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.