• Anonymous
  • Login
  • Register



JSON and REST Samples

Owners Niklas Heidloff Project Creation Feb 22, 2011
Contributors - Last Release Feb 22, 2011
Downloads 1625
Rating
(0 ratings)
Description JSON and REST Samples


This project has been merged into Social Enabler.

 

 

REST services and JSON have become more and more popular. Providing REST/JSON services opens up new capabilities to consume XPages application functionality in other types of applications. Additionally existing Dojo UI controls can be used and data can easily be bound to them. Furthermore the clean separation of the services and data on one hand side and the UI/markup on the other hand side allows easy caching and enables offline capabilities.

This project shows simple samples for how to handle JSON.

The XPages runtime comes with it's own JSON Library (e.g. com.ibm.commons.util.io.json.JsonJavaFactory) allowing the implementation of REST services using JSON. The XPages Extension Library includes already REST services for view entries. This project shows how to provide custom REST services for data from somewhere else (in this case from one document) and it shows how to do this without the extension library as prereq. While the mechanism in the extension library is more sophisticated, this sample shows a pragmatic interim solution.

The project also shows how to consume the REST/JSON services on client side. One XPage shows how to get the output of a service call in a JavaScript object.
Another XPage shows how to bind a REST service to a Dojo data grid control. This control can be populated via a REST GET requests. Furthermore cell values can be changed and be written back via REST PUT requests.

 

There are several resources available describing REST, JSON and Dojo: here, here, here, here, here and here.

 



Projects can have short and readable URLs, e.g. http://mobilecontrols.openntf.org.

You can request a short URL to your project by sending a mail to support at openntf dot org.
Owners are the people with maximal rights. For example they can create releases and add more contributors.

In order to define multiple owners use "," (comma) as separator.

Because of data privacy you cannot lookup other people's names but you have to type them in.
Enter the contributors or owners here who you want to receive notifications and questions by email.

In order to define multiple owners use "," (comma) as separator.

Because of data privacy you cannot lookup other people's names but you have to type them in.
In addition to the owners additional OpenNTF contributors have to be listed here. Contributors don't have the same access rights as owners, e.g. they cannot create releases.

In order to define multiple owners use "," (comma) as separator.

Because of data privacy you cannot lookup other people's names but you have to type them in.
Enter a short description of the project here (up to 100 characters).

The short description shows up in the project UI and in some of the views.
In this field you should enter a more detailed description of your project.

You can use the rich text editor for rich text formating. You can also enter HTML to embed objects, e.g. to embed a YouTube video or a screenshot of the project. In this case use '[' and ']' to mark the passthrough HTML as such.
A Catalog Release is for projects that are production ready and that are end-user "install friendly".

This property describes whether any release of this project has been added to the catalog.

Learn more about the catalog.
GitHub can be used as source control repository for OpenNTF projects. In this case the Issues from GitHub are used instead of the Defects from OpenNTF.

Contact ip-manager@openntf if you want to have a GitHub project created in the OpenNTF space.

Learn more about OpenNTF on GitHub