incubator-isis-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Haywood <>
Subject Re: a JSON-based RESTful protocol.
Date Fri, 24 Jun 2011 18:58:33 GMT
Hi Henry
Thanks for your interest in Isis. 

In fact, the "com.mycompany.myapp.Order|123" is just illustrative; the value used should be
considered opaque to the restful client and will actually be the string form of the internal
Oid class, which is assigned by the objectstore. For example, if using the in-memory object
store it is simply OID:123 etc, while my jpa object store (not yet part of the distribution)
would use ORD|123 (where ORD is the @Discriminator annotation in jpa api)

Hope that makes sense; will post here when there's more of the viewer implemented for you
to play with. 


Sent from my iPhone

On 24 Jun 2011, at 19:38, Henry Saputra <> wrote:

> Hi Dan,
> Is there a way to map the actual Java class name for the object such
> as com.mycompany.Order|123 to short name? This will help to make the
> API URL simpler.
> I am new with Apache Isis and naked object design but looking forward
> to implement it as prototype for our architecture.
> - Henry
> On Tue, Jun 14, 2011 at 2:39 PM, Dan Haywood <> wrote:
>> Alexander and I have (off-list) been throwing an idea or two about
>> developing a viewer-agnostic network protocol.  Alexander put a page on the
>> wiki about this a while back [1].
>> My thought are that we could support this using a JSON-based RESTful
>> protocol, perhaps as an extension/evolution of our current Restful viewer
>> (which currently supports only XHTML).
>> With that in mind, I've added a number of pages to the wiki to document what
>> this protocol might look like; [2] is the jumping off point, but see also
>> [3] for details on the typical representation of a domain object.
>> Comments/contributions welcome!
>> Dan
>> [1]
>> [2]
>> [3]

View raw message