Q. The capability to hide messaging behind a POJO interface.

View solution

Q. The most fundamental support for gateways comes from the Spring Integration class:-

View solution

Q. The SimpleMessagingGateway needs a request and a response channel, and it coordinates the rest.

View solution

Q. The first thing that the client configuration does is import a shared application context (to save typing if nothing else) that declares a JMS connection factor.

View solution

Q. Messages sent on the requests channel are forwarded to the:-

View solution

Q. The gateway element simply exists to identify the component and the interface.

View solution

Q. There is no coupling between the client facing interface exposed via the gateway component and the interface of the service that ultimately handles the messages.

View solution

Q. The service-activator is what handles actual processing and there’s no mention of a response channel, for either the service-activator, or for the inbound JMS gateway.

View solution

Q. Spring Batch provides a lot of flexibility and guarantees to your application, but it cannot work in a vacuum. To do its work:-

View solution

Q. There’s only one really useful implementation of the JobRepository interface, which stores information about the state of the batch processes in a database.

View solution

Q. To load the contents of a properties file (batch.properties) whose values you use to configure the data source.

View solution

Q. MapJobRegistry instance. This is critical—it is the central store for information regarding a given Job.

View solution

Q. SimpleJobLauncher, whose sole purpose is to give you a mechanism to launch batch jobs, where a “job” in this case is our batch solution.

View solution

Q. Spring Batch models solutions using XML schema.

View solution

Q. However, it’s important to wear another hat, that of a DBA, when writing applications.

View solution

Q. Indeed, a step could be considered the smallest unit of work for a job. Input (what’s read) is passed to the Step and potentially processed; then output (what’s written) is created from the step.

View solution

Q. Attribute to configure how many items will be processed before the transaction is committed all the input is sent to the writer.

View solution

Q. Class which delegates the task of delimiting fields and records within a file to a LineMapper, which in turn delegates the task of identifying the fields within that record, to LineTokenizer.

View solution

Q. The names and values for the named parameters are being created by the bean configured for the itemSqlParameterSourceProvider property, an instance of the interface

View solution

Q. There’s support for writing JMS:-

View solution