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 "REST support in STP"
(→Introduction) |
(→Introduction) |
||
Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
− | This page aims to define the basic processes on how to support REST in stp. There are two ways to support to create RESTfull service: * Exposing a database to RESTfull service directly | + | This page aims to define the basic processes on how to support REST in stp. |
+ | There are two ways to support to create RESTfull service: * Exposing a database to RESTfull service directly | ||
* Starting from importing some POJO class into a rest project, then add some REST annotations which defined in jsr311 specification | * Starting from importing some POJO class into a rest project, then add some REST annotations which defined in jsr311 specification | ||
+ | |||
+ | It is a multiple pages editor, which consists of following pages: | ||
+ | * service overview page (for service.xml file) | ||
+ | * service policy page (for policy.xml file, or wsdl file) | ||
+ | * service osgi page (for MANIFEST.MF file) | ||
+ | * service assemble page (for service.assemble file) | ||
+ | * service deploy.page (for service.deploy file) |
Revision as of 23:31, 6 November 2007
Introduction
This page aims to define the basic processes on how to support REST in stp. There are two ways to support to create RESTfull service: * Exposing a database to RESTfull service directly
- Starting from importing some POJO class into a rest project, then add some REST annotations which defined in jsr311 specification
It is a multiple pages editor, which consists of following pages:
* service overview page (for service.xml file) * service policy page (for policy.xml file, or wsdl file) * service osgi page (for MANIFEST.MF file) * service assemble page (for service.assemble file) * service deploy.page (for service.deploy file)