Changeset 96
- Timestamp:
- 05/22/05 19:19:24 (4 years ago)
- Files:
-
- trunk/doc/dsp-reference/tags.html (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
trunk/doc/dsp-reference/tags.html
r95 r96 76 76 <h3>Description:</h3> 77 77 <p> 78 The page tag is completely optional and is used to help DSP achi ve XML compliance should the need78 The page tag is completely optional and is used to help DSP achieve XML compliance should the need 79 79 arise. It is completely transparent and only serves to group multiple servlets together as a top- 80 80 level element. It is not allowed inside of any other tags nor is it allowed to contain any DSP tags … … 376 376 All dsp:out code blocks are coalesced into a single contract for the response handler. 377 377 They are combined in the order they are processed in the DSP page. 378 It is important to note that since an Inblock runs after the rest of the handler,378 It is important to note that since an out block runs after the rest of the handler, 379 379 it only has access to the response and request 380 380 parameters for the response handler. It is essentially within its own scope and will … … 397 397 398 398 <h3>Syntax:</h3> 399 <pre class='syntax'><dsp: out<i>[attributes]</i> > <i>[dsp:attribute]</i> </dsp:out></pre>400 <pre class='syntax'><dsp: out<i>[attributes]</i> /></pre>399 <pre class='syntax'><dsp:tag <i>[attributes]</i> > <i>[dsp:attribute]</i> </dsp:out></pre> 400 <pre class='syntax'><dsp:tag <i>[attributes]</i> /></pre> 401 401 402 402 <h3>Attributes:</h3>
