ZATS Richlet"

From Documentation
Line 2: Line 2:
 
{{ZATSEssentialsPageHeader}}
 
{{ZATSEssentialsPageHeader}}
  
ZATS Mimic also supports <javadoc>org.zkoss.zk.ui.Richlet</javadoc><ref>for more detail, please refer to [[ZK_Developer%27s_Reference/UI_Composing/Richlet]]</ref>. It just needs a few custom configuration for [http://www.zkoss.org/javadoc/latest/zats/org/zkoss/zats/mimic/DefaultZatsEnvironment.html DefaultZatsEnvironment] and the test code is no different with testing a ZUML file. The following is a simple Richlet example:
+
ZATS Mimic also supports <javadoc>org.zkoss.zk.ui.Richlet</javadoc><ref>for more detail, please refer to [[ZK_Developer%27s_Reference/UI_Composing/Richlet]]</ref>. It just needs a few custom configuration for [http://www.zkoss.org/javadoc/latest/zats/org/zkoss/zats/mimic/DefaultZatsEnvironment.html DefaultZatsEnvironment] and the test code is no different with testing a ZUML file. The following is a simple <tt>Richlet</tt> example:
  
 
'''web.xml'''
 
'''web.xml'''
Line 47: Line 47:
 
<references/>
 
<references/>
  
 +
When testing the <tt>Richlet</tt>, we only need to provide custom web configuration(such as web.xml and zk.xml) for <tt>DefaultZatsEnvironment</tt>. The default configuration ZATS Mimic used doesn't support Richlet. We can specify the ''' WEB-INF''' path for the testing environment through the overrode constructor of <tt>DefaultZatsEnvironment</tt>. The following is a typical example for testing <tt>Richlet</tt>:
  
 
+
<source lang="java" start="10" high="12, 15, 22">
 +
@Test
 +
public void test() {
 +
DefaultZatsEnvironment env = new DefaultZatsEnvironment("./src/main/webapp/WEB-INF");
 +
try {
 +
env.init("./src/main/webapp");
 +
DesktopAgent desktop = env.newClient().connect("/zk/foo");
 +
Label msg = desktop.query("#msg").as(Label.class);
 +
Assert.assertEquals("foo", msg.getValue());
 +
desktop.query("#btn").click();
 +
Assert.assertEquals("bar", msg.getValue());
 +
}
 +
finally {
 +
env.destroy();
 +
}
 +
}
 +
</source>
 +
* '''Line 12''': It specifies the folder path of web configuration for testing the <tt>Richlet</tt>.
 +
* '''Line 22''': If using the <tt>DefaultZatsEnvironment</tt> not <tt>Zats</tt> for testing, we should release it when the test finish.
  
 
{{ZATSEssentialsPageFooter}}
 
{{ZATSEssentialsPageFooter}}

Revision as of 04:34, 12 June 2012

WarningTriangle-32x32.png This page is under construction, so we cannot guarantee the accuracy of the content!

aowang



ZATS Mimic also supports Richlet[1]. It just needs a few custom configuration for DefaultZatsEnvironment and the test code is no different with testing a ZUML file. The following is a simple Richlet example:

web.xml

<servlet-mapping>
	<servlet-name>zkLoader</servlet-name>
	<url-pattern>/zk/*</url-pattern>
</servlet-mapping>

zk.xml

<richlet>
	<richlet-name>MyRichlet</richlet-name>
	<richlet-class>foo.MyRichlet</richlet-class>
</richlet>
<richlet-mapping>
	<richlet-name>MyRichlet</richlet-name>
	<url-pattern>/foo</url-pattern>
</richlet-mapping>

MyRichlet.java

public class MyRichlet extends GenericRichlet {
	public void service(Page page) throws Exception {
		final Label message = new Label("foo");
		Button button = new Button("go");
		button.addEventListener(Events.ON_CLICK, new EventListener() {
			public void onEvent(Event event) throws Exception {
				message.setValue("bar");
			}
		});
		button.setId("btn");
		message.setId("msg");
		button.setPage(page);
		message.setPage(page);
	}
}
  • Line 12, 14, 16: After clicking the button, the text of label will be changed.

Notes

  1. for more detail, please refer to ZK_Developer's_Reference/UI_Composing/Richlet

When testing the Richlet, we only need to provide custom web configuration(such as web.xml and zk.xml) for DefaultZatsEnvironment. The default configuration ZATS Mimic used doesn't support Richlet. We can specify the WEB-INF path for the testing environment through the overrode constructor of DefaultZatsEnvironment. The following is a typical example for testing Richlet:

@Test
public void test() {
	DefaultZatsEnvironment env = new DefaultZatsEnvironment("./src/main/webapp/WEB-INF");
	try {
		env.init("./src/main/webapp");
		DesktopAgent desktop = env.newClient().connect("/zk/foo");
		Label msg = desktop.query("#msg").as(Label.class);
		Assert.assertEquals("foo", msg.getValue());
		desktop.query("#btn").click();
		Assert.assertEquals("bar", msg.getValue());
	}
	finally {
		env.destroy();
	}
}
  • Line 12: It specifies the folder path of web configuration for testing the Richlet.
  • Line 22: If using the DefaultZatsEnvironment not Zats for testing, we should release it when the test finish.



Last Update : 2012/06/12

Copyright © Potix Corporation. This article is licensed under GNU Free Documentation License.