Hi Ged, As per your "drill down" comment the REST equivalent of WSDL is achieved by following the HREF links eg: /restful/ /restful/domain-types /restful/domain-types/dom.todo.ToDoItems /restful/domain-types/dom.todo.ToDoItems/actions/notYetComplete /restful/domain-types/TODO /restful/domain-types/TODO/properties/cost /restful/domain-types/java.math.BigDecimal
I don't think RO provides a single JSON for the whole app, my gut feeling is to have 1 JSON per Type then navigate through them. A single JSON could get complex where there are multiple sub-objects / dependencies. HTH Mike Burton On 8 Jan 2014, at 08:55, Ged Byrne <ged.by...@gmail.com> wrote: > Hi All, > > Is there an equivalent to the WSDL and XSD documents in the RestfulObjects > standard? > > Looking at it from a worflow perspective, the WSDL/XSD serve the following > purpose: > > 1. We have an external third party that needs to integrate with our > services. > 2. We don't have proper DevOps yet so it will take a couple of months to > arrange access to our systems. > 3. We're using SOAP, so I can send them our WSDLs and XSDs. They can > then use these to build stubs. > 4. When proper intergration finally occurs, we are at least able to > count on binary comparability, even though their stubs got all the behavior > wrong. > > Now that we are developing with ISIS we no longer have SOAP's WSDL and XSD > to pass around. So how does the above workflow work now? > > Is there a document like the WSDL/XSD? > > I see there are descriptions provided by the RO Viewer that I can drill > down through. Is there any way of obtaining the JSON for the whole app as > a single document? > > Or should I just send them regular updates of our domain objects and > instructions to do a maven clean install? > > Regards, > > > > Ged
