classic HTML links. Following the analogy with GUI frameworks, we can consider Wicket link as a “click” event handler: its purpose is to perform some actions (on server side!) when the user clicks on class of the 12 target page. In this way a new instance of AnotherPage will be created each time we click on the link. The other version of setResponsePage takes in input a page instance instead of a page paragraph we had a first taste of Wicket links and we have seen how they can be considered as a “click” event listener and how they can be used to navigate from a page to another. 13 Chapter 5. Wicket

classic HTML links. Following the analogy with GUI frameworks, we can consider Wicket link as a “click” event handler: its purpose is to perform some actions (on server side!) when the user clicks on class of the target page. In this way a new instance of AnotherPage will be created each time we click on the link. The other version of setResponsePage takes in input a page instance instead of a page paragraph we had a first taste of Wicket links and we have seen how they can be considered as a “click” event listener and how they can be used to navigate from a page to another. 14 Chapter 5. Wicket

classic HTML links. Following the analogy with GUI frameworks, we can consider Wicket link as a “click” event handler: its purpose is to perform some actions (on server side!) when the user clicks on class of the target page. In this way a new instance of AnotherPage will be created each time we click on the link. The other version of setResponsePage takes in input a page instance instead of a page paragraph we had a first taste of Wicket links and we have seen how they can be considered as a “click” event listener and how they can be used to navigate from a page to another. 13 Chapter 5. Wicket

label = new Label("label","Hello!"); label.setOutputMarkupId(true); label.add(new AjaxEventBehavior("click") { @Override protected void onEvent(AjaxRequestTarget target) { //Do my to handle AJAX events. ● With Wicket 8 an AJAX click handler can be written leveraging lambdas in the following way: AjaxEventBehavior.onEvent("click", target -> target.add(component)); Testing with wicket.util.tester.WicketTester. This utility class provides a set of methods to render a component, click links, check page content, etc... Testing the response ● WicketTester allows us to access to the

classic HTML links. Following the analogy with GUI frameworks, we can consider Wicket link as a “click” event handler: its purpose is to perform some actions (on server side!) when the user clicks on class of the target page. In this way a new instance of AnotherPage will be created each time we click on the link. The other version of setResponsePage takes in input a page instance instead of a page paragraph we had a first taste of Wicket links and we have seen how they can be considered as a “click” event listener and how they can be used to navigate from a page to another. 14 Chapter 5. Wicket

back-channel system-to-system (as for example for a login) communication. Examples of events may include a click on a link on a web page, a login, a form submission, a page view or any other time-stamped action org/schemas/json/events/click/1-0-0", "$schema": "https://json-schema.org/draft/2019-09/schema", "self": { "vendor": "org.apache.unomi", "target": "events", "name": "click", "format": "jsonschema" = wem.buildEvent('click', wem.buildTarget('buttonId', 'button'), wem.buildSourcePage()); wem.collectEvent(clickEvent, function (xhr) { console.info('Click event successfully

Apache Unomi at the following URL : http://localhost:8181/tracker Simply modify the form values and click submit and it will perform all the steps we are describing below. So here is the form we want to back-channel system-to-system (as for example for a login) communication. Examples of events may include a click on a link on a web page, a login, a form submission, a page view or any other time-stamped action "Increment tweet number", "description": "Increments the number of times a user has tweeted after they click on a tweet button" }, "raiseEventOnlyOnceForSession": false, "condition": { "type": "eventTypeCondition"

= form.getOneHtmlElementByAttribute("input", "type", "submit"); HtmlPage newMessagePage = submit.click(); Kotlin val form = createMsgFormPage.getHtmlElementById("messageForm") val summaryInput = createMsgFormPage submit = form.getOneHtmlElementByAttribute("input", "type", "submit") val newMessagePage = submit.click() Finally, we can verify that a new message was created successfully. The following assertions use summary, String text) throws Exception { setSummary(summary); HtmlPage result = submit.click(); boolean error = CreateMessagePage.at(result); return (T) (error ? new CreateMessagePage(result)

You can install further hawtio plugins if you wish to have further functionality. Artemis Tab Click Artemis in the top navigation bar to see the Artemis specific plugin. (The Artemis tab won't appear Operations Creating a new Address To create a new address simply click on the broker or the address folder in the jmx tree and click on the create tab. Once you have created an address you should be clicking on the send tab. Creating a new Queue To create a new queue click on the address you want to bind the queue to and click on the create tab. Once you have created a queue you should be able to

You can install further hawtio plugins if you wish to have further functionality. Artemis Tab Click Artemis in the top navigation bar to see the Artemis specific plugin. (The Artemis tab won't appear Operations Creating a new Address To create a new address simply click on the broker or the address folder in the jmx tree and click on the create tab. Once you have created an address you should be Management Console 213 Creating a new Queue To create a new queue click on the address you want to bind the queue to and click on the create tab. Once you have created a queue you should be able