XML Namespaces"
m |
|||
Line 26: | Line 26: | ||
</n:table> | </n:table> | ||
</source> | </source> | ||
+ | |||
+ | where <tt>n:table</tt>, <tt>n:tr</tt> and <tt>n:td</tt> are native, i.e., they are generated directly to the client without creating a component for each of them. | ||
For more information, please refer to [[ZUML Reference/ZUML/Namespaces|ZUML Reference]]. | For more information, please refer to [[ZUML Reference/ZUML/Namespaces|ZUML Reference]]. |
Revision as of 06:21, 3 December 2010
In a ZUML document, a XML namespace is used to identify either a special functionality or a component set. We call the former as a standard namespace, while the later as a language.
Standard Namespaces
For example, the client namespace is used to identify that a XML attribute shall be interpreted as a client-side control.
In the following example, w:onFocus is a client-side listener since w: is specified, while onChange is
<combobox xmlns:w="client" w:onFocus="this.open()" onChange="doOnChange()"/>
The native namespace is another standard namespace used to indicate a XML element shall be generated natively, rather than a component. For example,
<n:table xmlns:n="native">
<n:tr>
<n:td>Username</n:td>
<n:td><textbox/></n:td>
</n:tr>
<n:tr>
<n:td>Password</n:td>
<n:td><textbox type="password"/></n:td>
</n:tr>
</n:table>
where n:table, n:tr and n:td are native, i.e., they are generated directly to the client without creating a component for each of them.
For more information, please refer to ZUML Reference.
Languages
Version History
Version | Date | Content |
---|---|---|