JavaEE and Wildfly Module 3: Messaging

featuring JMS and Message Driven Beans (MDB).

Learn how to send and receive messages using the Java Messaging Service (JMS) with the WildFly Application Server.
You'll be using the Point-to-Point and Publish-Subscribe models, and you'll find out how to use batching and transactions to ensure message delivery.
With this course, you can build robust and scalable architectures!

Pre-requisites

You'll need some experience of working with and deploying to WildFly - you can get this by studying the first two modules in this series.

Having problems? check the errata for this course.

1	Course Introduction	Preview 22m 0s
An overview of the JMS Library. Why do Messaging? The Point-to-Point and Publish/Subscribe models.
2	Sending a Message	Watch 30m 34s
Sending your first message to WildFly's ActiveMq Broker.
3	Receiving Messages	Watch 46m 35s
How to pull messages from the Queue.
4	Tuning Messages	Watch 20m 48s
How to set an expiry time and priority - and what guarantees do these settings offer?
5	Browsing Queues	Watch 15m 20s
You can write code to list the contents of a Queue.
6	The Publish-Subscribe Model	Watch 20m 28s
This model allows multiple receivers via a "subscription". This is more flexible than point-to-point, but it is also more complicated - you'll need to understand "durable" subscriptions.
7	Transactions and Batching	Watch 31m 52s
Often, you need to guarantee a message is definitely consumed, and that it is processed once only - we see how to do that here.
8	Sending from EJBs	Watch 25m 38s
Sending a message from an EJB is much easier than doing so manually.
9	Message Driven Beans (MDB)	Watch 19m 38s
An extremely useful form of EJB, an MDB is permanently connected to a Queue. We also see how multiple MDBs are pooled to give concurrent processing.
10	Handling Problems	Watch 20m 8s
What happens if a message fails to be processed?
11	Message Redelivery	Watch 21m 31s
We use ActiveMqs redeliver feature to handle transient problems such as network failure.