User:Paowang/ZATS Richlet

This page is under construction, so we cannot guarantee the accuracy of the content!

ZATS Mimic also supports to test Richlet. 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

---

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 folder path for the testing environment through the 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 we use the DefaultZatsEnvironment not Zats, it should be released when the test finish.