If you are not familiar with XML, please take a look at [[ZK Developer's Reference/UI Composing/ZUML/XML Background|XML Background]] first. =An XML Element Represents a Component=

...necessary. The advantage is that a composite component can extend from any component, such as <javadoc>org.zkoss.zul.Row</javadoc>, such that it is easier to fi ...acro component if applicable (since it is easier), while using a composite component otherwise.

...ng, java.lang.String, org.zkoss.zk.ui.Component, java.util.Map)">org.zkoss.zk.ui.Execution</javadoc> and many others. In addition, <javadoc>org.zkoss.zk.ui.Executions</javadoc> provides a similar collection of shortcuts so that

...ment any functionality you want. For more information please refer to [[ZK Component Development Essentials]]. ...s and composing them in a ZUML page. In other words, we could define a new component by expressing it in a ZUML page. It works like composition, macro expansion

...instantiated to represent a regular macro. By default, <javadoc>org.zkoss.zk.ui.HtmlMacroComponent</javadoc> is assumed (and instantiated). However, you ...5.0.4 or earlier, please invoke <javadoc method="afterCompose()">org.zkoss.zk.ui.HtmlMacroComponent</javadoc> instead.</ref>, such that the template and

<?component name="''myName''" templateURI="''/mypath/my.zul''" ?> <?component name="''myName''" macroURI="''/mypath/my.zul''" [inline="true|'''false'''"]