title: Is still useful to implement EJB with RMI when you can implement Web Services (SOA/REST)?
body: <p>This might sound similar to <a href="https://stackoverflow.com/questions/2013793/web-services-vs-ejb-vs-rmi-advantages-and-disadvantages">this</a>, but it's not.</p>
  
  <p>I kind of understand EJB and RMI, and I have been working with web services under SOA for a while. I want to know why is useful to work using EJB exposing remote interfaces under RMI instead of publishing Web Services (SOA/REST, but mostly SOA). I'm not asking which one is better, just I want to know a very good reason of why should I prefer to implement EJB with remote interfaces over Web Services.</p>
  
  <p>I have reviewed a lot of webpages but all seemed outdated. Until now, what I have is that EJB exposing remote interfaces is only better than WS when integrating with Java legacy system. If I want to manage transactions I could implement EJB with local interfaces. Also I don't think choosing EJB over RMI is more efficient than a Web Service interface. </p>
  
  <p>Am I right? Is there something I'm missing?</p>
  
  <p>Really thanks in advance.</p>