fields with the corresponding object fields and vice versa. Wicket comes with an intuitive and flexible mechanism that does this mapping for us without any configuration overhead (using a convention executed, such as opening a Hibernate/JPA session and closing it when code has terminated. A more flexible way to interact with the request processing is to use the listener interface org.apache.wicket query string parameters (like ?paramName1=paramValu1¶mName2=paramValue2…). Wicket offers a more flexible and object oriented way to do this with models (we will see them in the next chapter). However

fields with the corresponding object fields and vice versa. Wicket comes with an intuitive and flexible mechanism that does this mapping for us without any configuration overhead (using a convention executed, such as opening a Hibernate/JPA session and closing it when code has terminated. A more flexible way to interact with the request processing is to use the listener interface org.apache.wicket query string parameters (like ?paramName1=paramValu1¶mName2=paramValue2…). Wicket offers a more flexible and object oriented way to do this with models (we will see them in the next chapter). However

fields with the corresponding object fields and vice versa. Wicket comes with an intuitive and flexible mechanism that does this mapping for us without any configuration overhead (using a convention executed, such as opening a Hibernate/JPA session and closing it when code has terminated. A more flexible way to interact with the request processing is to use the listener interface org.apache.wicket query string parameters (like ?paramName1=paramValu1¶mName2=paramValue2…). Wicket offers a more flexible and object oriented way to do this with models (we will see them in the next chapter). However

fields with the corresponding object fields and vice versa. Wicket comes with an intuitive and flexible mechanism that does this mapping for us without any configuration overhead (using a convention executed, such as opening a Hibernate/JPA session and closing it when code has terminated. A more flexible way to interact with the request processing is to use the listener interface org.apache.wicket query string parameters (like ?paramName1=paramValu1¶mName2=paramValue2…). Wicket offers a more flexible and object oriented way to do this with models (we will see them in the next chapter). However

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 17.1. Official Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failover so you can guarantee zero message loss or duplication in event of server failure. • Hugely flexible clustering. Create clusters of servers that know how to load balance messages. Link geographically over unreliable connections to form a global network. Configure routing of messages in a highly flexible way. Chapter 3. Messaging Concepts Apache ActiveMQ Artemis is an asynchronous messaging system

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.9. Container Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.11. GraalVM Native Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.2.2. GraalVM Native Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.9. Container Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.11. GraalVM Native Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.2.2. GraalVM Native Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 17.1. Official Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failover so you can guarantee zero message loss or duplication in event of server failure. • Hugely flexible clustering. Create clusters of servers that know how to load balance messages. Link geographically over unreliable connections to form a global network. Configure routing of messages in a highly flexible way. Chapter 3. Messaging Concepts Apache ActiveMQ Artemis is an asynchronous messaging system

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 17.1. Official Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failover so you can guarantee zero message loss or duplication in event of server failure. • Hugely flexible clustering. Create clusters of servers that know how to load balance messages. Link geographically over unreliable connections to form a global network. Configure routing of messages in a highly flexible way. Chapter 3. Messaging Concepts Apache ActiveMQ Artemis is an asynchronous messaging system

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 17.1. Official Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failover so you can guarantee zero message loss or duplication in event of server failure. • Hugely flexible clustering. Create clusters of servers that know how to load balance messages. Link geographically over unreliable connections to form a global network. Configure routing of messages in a highly flexible way. Chapter 3. Messaging Concepts Apache ActiveMQ Artemis is an asynchronous messaging system