Trace:
Differences ¶
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| en:tutorial:action-creation [2006/09/25 08:39] – doubleface | en:tutorial:action-creation [2006/09/26 16:04] – doubleface | ||
|---|---|---|---|
| Line 13: | Line 13: | ||
| Knowing the type of request processed and the action, Jelix knows the type of the answer to be generated, and thus controls more or less the response generation. Thus, even the error case (an exception or other) occurring during the processing of the action, the exit format will always be the awaited one. A client who calls a web service with xmlrpc, will thus have no matter what happens, a response in the xmlrpc format. That brings a certain robustness to the application. | Knowing the type of request processed and the action, Jelix knows the type of the answer to be generated, and thus controls more or less the response generation. Thus, even the error case (an exception or other) occurring during the processing of the action, the exit format will always be the awaited one. A client who calls a web service with xmlrpc, will thus have no matter what happens, a response in the xmlrpc format. That brings a certain robustness to the application. | ||
| + | |||
| ===== Implementing an action ===== | ===== Implementing an action ===== | ||
| Line 37: | Line 38: | ||
| There is an index() method, which retrieves the " | There is an index() method, which retrieves the " | ||
| + | |||
| + | |||
| + | ==== Response object ==== | ||
| + | |||
| + | In the $rep variable, you get an object extending the jResponse class. Since we specified, that the response is the HTML type, you actually get a jResponse Html object (extending jResponse). You will see later that there are other types of responses, and that you can produce your own response objects. | ||
| + | |||
| + | The jResponseHtml object handles the generation of a HTML response (ie an HTML page). It generates automatically the < | ||
| + | |||
| + | <code php> | ||
| + | | ||
| + | </ | ||
| + | |||
| + | And the browser will receive : | ||
| + | |||
| + | <code xml> | ||
| + | < | ||
| + | < | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | All the body of the page, i.e the content of the html tag < | ||
| + | Before beginning to code, let's see the content of the template | ||
| + | |||
