Changes between Version 13 and Version 14 of RESTController


Ignore:
Timestamp:
11/20/09 01:11:51 (12 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • RESTController

    v13 v14  
    4848The argument list is interpreted as follows:
    4949
    50   * '''empty argument list''' accesses to all/any records of the resource
     50  * '''empty argument list''' access to all/any records of the resource
    5151  * '''<id>''' access to record #<id> of the resource
    5252  * '''<method>''' <method> access to all/any records of the resource
     
    5656  * '''<id>/<component>/<method>''' <method> access to all/any component records for the record #<id> of the resource
    5757
    58 If '''<id>''' is omitted from the URL while the argument list is not empty, then the last used <id> for this resource will be used. This feature can be used for cascading or returning UI actions. The last record ID can be explicitly cleared by sending a request to the primary resource with ''clear'' as method. At login/logout as well as after a ''delete'' action, the ID memory is automatically cleared, of course.
     58If '''<id>''' is omitted from the URL while a <method> or a <component> is specified, then the last used <id> for this resource will be used. This feature can be used for cascading or returning UI actions. The last record ID can be explicitly cleared by sending a request to the primary resource with ''clear'' as method. At login/logout as well as after a ''delete'' action, the record ID memory is automatically cleared, of course.
    5959
    6060You may pass a record ID for the component at the end of the arguments list to access a particular component record - which would produce an error message if these two records do not belong together. Component record ID's are not remembered.