Hi Dan, I went through several several REST api tutorials. The first thing I understood is that REST is almost similar to HTTP (Isn't it?).
In sample application I had some experiences with restful object viewer. I'm really impressed the way it provide all data through JSON. However as always I have several problems. 1. At the very beginning I went to the url - http://localhost:8080/restful/ It gave following output. { links: [ { rel: "self", href: "http://localhost:8080/restful/";, method: "GET", type: "application/json;profile="urn:org.restfulobjects/homepage"" }, { rel: "user", href: "http://localhost:8080/restful/user";, method: "GET", type: "application/json;profile="urn:org.restfulobjects/user"" }, { rel: "services", href: "http://localhost:8080/restful/services";, method: "GET", type: "application/json;profile="urn:org.restfulobjects/list"" }, { rel: "version", href: "http://localhost:8080/restful/version";, method: "GET", type: "application/json;profile="urn:org.restfulobjects/version"" }, { rel: "types", href: "http://localhost:8080/restful/domainTypes";, method: "GET", type: "application/json;profile="urn:org.restfulobjects/typelist"" } ], extensions: { } } I'm completely ok with the content of the output. But the thing I need to clarify is from where did this json object come from. And can we change the content of this output. (As an example: can we remove domainTypes link from this JSON object?). If so how? 2. I consist of a link - "http://localhost:8080/restful/domainTypes"; but all we need is "http://localhost:8080/restful/services"; because at gui level we interact with those Services (am I correct?) not with those domainTypes. If so what is the use of domain types to gui level? 3. If I speak straight, is the purpose of project to map these json objects details to android gui? On Thu, Apr 11, 2013 at 12:25 AM, Dan Haywood <d...@haywood-associates.co.uk> wrote: > > > > On 10 April 2013 16:56, DImuthu Upeksha <dimuthu.upeks...@gmail.com> wrote: >> >> >> And one thing about DomainObjectContainer: Is it responsible for >> keeping user information? (I mean session details) > > > From DOC you can find out the identity of the current user, (the getUser()) > method, but that's all. There *isn't* anyway to obtain the HttpSession (if > that's what you were thinking). I can think of a way to do it, but it's not > come up as a requirement, yet. > > Isis also has the concept of the ProfileStore, the idea being that this is a > place for the viewers to store information such as a users' preferences etc. > But this isn't formally exposed by the DOC, so isn't available to domain > objects. You could write your own domain service to store this sort of > info, if you wanted, though. > > HTH > Dan > -- Regards W.Dimuthu Upeksha Undergraduate Department of Computer Science And Engineering University of Moratuwa, Sri Lanka
