Dear Maheed,
Research & development of restful web services and its integration in
existing DHIS2 frameworks begins with an empirical case study for providing
solution to a very complex use case scenario in which one slandered
statical application developed inside certain environment running on
certain platform on certain virtual machine with certain attached database
with certain object relational data base schema can communicate with
another similar statical application developed in different environment
running on different platform on different virtual machine with different
data base with different object relational schema.
Here in DHIS2, we achieved solution for this complex scenario by developing
an intermediate middle-ware application programme interface or we can say
like an intermediate component like DHIS2 WEB-API or more simply we can say
like a connector which brings an intermediate interface from where DHIS2
can communicate with other similar statical application or multiple
applications like one to one or one to many relationship.
Interesting thing in DHIS2 WEB-API brings intermediate communication
between another multiple applications, and for that it follow certain rules
and regulation which we can say like protocol for communication like
http,ftp,sftp etc and on the top of these protocol these multiple statical
applications interact with each other and exchange some data as per the
request in the form of expected representational state like
json,xml,cvs,atom etc with each other and this way we solve these complex
issues.
Perhaps, I think as per your request and query which evolves with two
different aspects in which one addresses issue for understanding and doing
certain DHIS2 application programme interface analytical study for that you
are looking to access demo web-api with certain request with data and
another you have find some result as response in certain format of data
that you seems might be not as expected and has been addressed as an
web-appl bug.
If i am right, than for your first query, i think DHIS2 restful web-api
services is not as the exact tool for doing this analytical study. Rather,
you can take a help of DHIS2-API documentation, please find as i have
attached in the attachment. And second, it returns with some data in the
form of response after sending some http request, which does’t brings data
as should be expected and might be treated as bug in existing functionality
and should be resolved in up-comming releases.
Brajesh
From: Bob Jolliffe bobjolliffe@gmail.com
Date: Mon, 25 Aug 2014 16:17:58 +0100
Subject: Re: [Dhis2-users] [Dhis2-devs] API resources navigation
To: Knut Staring knutst@gmail.com
Cc: dhis2-users dhis2-users@lists.launchpad.net,
“dhis2-devs@lists.launchpad.net” dhis2-devs@lists.launchpad.net
Yes that will be nice. I also miss the api navigation … didn’t realize
how much I used it till it went 
On 25 August 2014 15:08, Knut Staring knutst@gmail.com wrote:
Hi Maheed,
This is intentional. We do agree that the previous interface was much
easier to navigate, but it had other issues that needed fixing. We hope
someone can create a nice App with as nice (or even nicer) navigation as
before - probably it could be a student project this fall.
Knut
On Mon, Aug 25, 2014 at 2:13 PM, Maheed Ramadan maheed.ramadan@nrc.no
wrote:
Dear All,
I have the latest version of DHIS 2.16 and I am trying to access the
api/resources endpoint in my browser and the following result is
displaying:
