13.6. Exercises
13.1 JAXM using a messaging provider: Alter the example to use a messaging provider. A messaging provider that runs as a servlet is included with the JAXM early access implementation.
13.2 JaxmGameServer processing game requests: The current design of the JaxmGameServer has it initiating messages to the client. This might be seen in an Enterprise Application Integration use of JAXM, but not in a typical Web Service. Because JAXM has no publish-subscribe mode, a “push” distribution of game results does not really work if we consider multiple clients. After the JAXM client code is introduced in Chapter 14, rework the example so that the client requests game results, rather than having the servlet push results to the client.
Get J2EE™ and JAX™: Developing Web Applications and Web Services now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
