Clarifying a bit…
We are adding REST to the Epicor proprietary approach the client uses and to SOAP and allowing it as an integration approach. We are also using it internally for released products like Active Home Page, Epicor Data Discovery and Mobile CRM (and a few more in the pipeline not announced). Actually if you squint right, ECC used a preview version of REST a long time ago and Social uses a preview OData syntax.
Consider IF Epicor went to full time REST instead of the proprietary wcf binding Epicor that ERP 10 has when the client impl is available.
If we did that would be a direct drop in with nothing changing to the consumers of an Impl. No one can get in the middle of that binding today to make sense of the byte that flies over the wire. SOAP and now REST are the integration options and those would not change just because an invisible protocol changes from one byte over wcf to another byte over ‘rest’.
The thing to concentrate upon is why are you choosing REST vs SOAP vs IMPL?
SOAP has some advanced options nothing else can touch around WS*.
REST has the flexibility to run anywhere.
IMPLs have the full ‘ERP goodness’ of all the features there.
Choose the right tool for the job. We are giving you options so you don’t HAVE to do it the Epicor™ way. Use your data the way you want.