Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Texo/JSON REST Web Services"
< Texo
(→Introduction) |
(→Introduction) |
||
| Line 3: | Line 3: | ||
== Introduction == | == Introduction == | ||
| − | The Texo JSON web service support uses the Texo [[Texo/Download_and_Install#Using_Texo_at_runtime_outside_of_Eclipse.2FOSGI|runtime]] libraries | + | Texo JSON web services allow you to connect client-side user interfaces to a standard JPA enabled web container. The client side can be based on a RIA library such as [http://www.sencha.com|sencha/extjs]] or a mobile web solution. In the future also RCP clients will be supported. |
| + | |||
| + | The Texo JSON web service support uses the Texo [[Texo/Download_and_Install#Using_Texo_at_runtime_outside_of_Eclipse.2FOSGI|runtime]] libraries. | ||
| + | |||
| + | The Texo JSON webservice support the following operations: | ||
| + | * Retrieve using GET http requests: using queries, requesting individual objects, all instances of a type | ||
| + | * Delete operation through the HTTP Delete method | ||
| + | * Update and Insert through POST/PUT | ||
| + | |||
| + | On each request Texo returns a structured response based on a schema. The response contains retrieved data, metadata (like record count), updated objects and result information. | ||
== Response XML Schema == | == Response XML Schema == | ||
Revision as of 03:39, 3 April 2012
Contents
Introduction
Texo JSON web services allow you to connect client-side user interfaces to a standard JPA enabled web container. The client side can be based on a RIA library such as [1]] or a mobile web solution. In the future also RCP clients will be supported.
The Texo JSON web service support uses the Texo runtime libraries.
The Texo JSON webservice support the following operations:
- Retrieve using GET http requests: using queries, requesting individual objects, all instances of a type
- Delete operation through the HTTP Delete method
- Update and Insert through POST/PUT
On each request Texo returns a structured response based on a schema. The response contains retrieved data, metadata (like record count), updated objects and result information.