"better" in this case is subjective. If there is some unique functionality you need or you feel more comfortable using ES go for it. Currently from an MII development perspective I think using JCo provides a quicker and cleaner implementation. Also in the wild you are more likely to get access or a resource on the abap/rfc side from a client than you are on the web service side. ' my advice but I don't have a bias I have done both. If you really want to get some idea to help make an architectural decision pick a few scenarios and implement them both ways.
↧
