Changes between Version 13 and Version 14 of RESTController

Timestamp:

11/20/09 01:11:51 (15 years ago)

Author:

Dominic König

Comment:

--

RESTController

@@ -48 +48 @@
 The argument list is interpreted as follows:
 
-  * '''empty argument list''' accesses to all/any records of the resource
+  * '''empty argument list''' access to all/any records of the resource
   * '''<id>''' access to record #<id> of the resource
   * '''<method>''' <method> access to all/any records of the resource
@@ -56 +56 @@
   * '''<id>/<component>/<method>''' <method> access to all/any component records for the record #<id> of the resource
 
-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.
+If '''<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.
 
 You 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.