Hi Dan, I might have a problem that needs the inverse - there is an external (Joomla) application that can expose objects (that would map onto Isis domain objects) via a REST interface[1] - represented as either JSON or XML.
How can I use that REST interface to read (from) and update (to) the external app? Basically, for certain domain objects (the "user" object), the "read" and "write" must be achieved via REST while for all other domain objects the default object store would be used, I guess. Does this make sense? Is this possible? It would even be acceptable if I could only access the external REST interface via an Isis service that internally calls the external application... Regards, Kevin [1] http://techjoomla.com/joomla-extension-news/joomla-rest-api.html On 18 Sep 2011 at 18:36, Dan Haywood wrote: > Hi all, > Following on from a mail I sent back in July [1], I've been working on a > specification to define a standard way of making domain object models > available over REST through a set of JSON representations. > > The intention is for the Isis json-viewer to implement this spec; hence > ISIS-109 [2]. In addition, the Nakedobjects MVC (framework on .NET) [3] > also intending to implement the same spec. So there may be an > opportunity to do some community building across platforms... you never > know. > > Anyway, if anyone here is interested in REST, I'd really be interested > in your feedback. And/or, if you can suggest any other communities (eg > within Apache?), who might be interested, that would also be really great. > > Cheers > Dan > > > [1] http://www.mail-archive.com/[email protected]/msg02037.html > [2] https://issues.apache.org/jira/browse/ISIS-109 > [3] http://nakedobjects.net/home/index.shtml >
