Spring MCQ Quiz Hub

JMS sender and receiver classes can also extend to retrieve a JMS template:-

When you need access to the JMS template.

Spring provides an implementation of SimpleMessageConvertor to handle the translation of a JMS message received.

y default, the JMS template uses SimpleMessageConverter for converting TextMessage to or from a string.

For your front desk and back office classes, you can send and receive a map using the:-

When you call the receive() method on a JMS message consumer to receive a message.

EJB component which was introduced for asynchronous reception of JMS messages.

MDB must implements interfaces:-

In EJB 3.0, an MDB can be a POJO that implements the MessageListener interface and is annotated with the:-

You create a message listener to listen for JMS messages. This negates the need for the approach taken in BackOfficeImpl in previous recipes.

A message listener must implement the:-

When a JMS message arrives, the onMessage() method will be called with the message as the method argument.

Method to convert MapMessage Object into Spring runtime exception JmsException.

Spring provides several types of message listener containers:-

If you have a transaction requirement in receiving messages, you have to use:-

You have to set the delegate property of MessageListenerAdapter to your target bean.

Using Spring JMS support with a very simple instance of:-

ActiveMQ, provides only one pooled connection factory class alternative.

It caches consumers correctly, or use Spring ConnectionFactory implementations.

Implementation which returns the same underlying JMS connection each time (which is thread-safe according to the JMS API) and ignores calls to the close() method.

Integration of Spring which has each application produce files of shared data for others to consume.

Integration of Spring which has the applications store the data they want to share in a common database.

Integration of Spring which has each application expose some of its procedures so that they can be invoked remotely and have applications invoke them to initiate behavior and exchange data.

Integration of Spring which has each application connect to a common messaging system and exchange data and invoke behavior using messages.

Using an ESB lets you hide the origin of the message from the code that’s handling it.

As with a standard MDP, a configuration for the ConnectionFactory exists.

The configuration starts with the inboundHelloJMSMessageChannel channel, which tells Spring Integration what to name the point-to-point connection from the message queue to the:-

An adapter is a component that knows how to speak to a specific type of subsystem and translate messages on that subsystem into something that can be used in the Spring Integration bus only.

A service-activator, however, only helps you invoke your application’s business logic on receipt of a message.

The next component, a service-activator, listens for messages coming into that channel and invokes the bean referenced by the:-

Headers Found in Spring Integration Messages:-

Some header values are specific to the type of the source message payload.

Component-specific headers are the constants defined for files on:-

Annotation to get access to header metadata:-

The code for the service-activator has changed to reflect the fact that you’re expecting a message containing a message of type:-

To send a message into the bus and transform it before working with it further.

Spring Integration provides a transformer message endpoint to permit the augmentation of the message headers.

Spring Integration provides the ability to catch exceptions and send them to an error channel of your choosing. By default, it’s a global channel called :-

The errorChannel doesn’t need to be a service-activator.

All errors thrown from Spring Integration components will be a subclass of:-

One way to discriminate by Exception type is to use:-

Sending all the errors to the same channel can eventually lead to a large switch-laden class that’s too complex to maintain.

You can explicitly specify on what channel errors for a given integration should go.

Spring Integration will use that header and forward errors encountered in the processing of this message to that channel.

To fork the process flow from one component to many, either all at once or to a single one based on a predicate condition.

A splitter takes an input message and asks you, the user of the component, on what basis it should split the Message.

Spring Integration ships with useful splitters that require no customization.

Return type of the method annotated by the @Splitter annotation is of type:-

Annotation which collects a series of messages (based on some correlation that you help Spring Integration make between the messages).

To determine how many messages to read until it can stop:-