From the course: Learning JakartaEE

Unlock this course with a free trial

Join today to access over 25,500 courses taught by industry experts.

Using Jakarta Messaging

Using Jakarta Messaging

- [Instructor] Let me now demonstrate how Jakarta messaging has been used in practice in the support ticket notification system. Starting from the destinations, I'm in the GlassFish administration console. There you can see under Resources a branch called JMS Resources. Indeed, if you expand the destination Resources, there are the three queues defined, TicketQueue, TicketAcceptQueue, and TicketDoneQueue. If you click on the TicketQueue, for example, it has a JNDI name of jms/GlassFishTicketQueue, and its resource type is jakarta.jms.Queue. The other two queues would be the same. Back in chapter two, I took you through in detail how to set these up. So the important thing to note here is that GlassFish is the Jakarta messaging provider for this application. Back in the ID, now let's get to the Jakarta messaging clients, that is the producers and the consumers. Going back to the support-ticket-app, I'll start with the message producers. For the first scenario, that is for the…

Contents