Q. The API surfaces a Paging object, which works something like Criteria in Hibernate.

View solution

Q. To take an input file or a payload and reliably, and systematically, decompose it into events that an ESB can work with:-

View solution

Q. Spring Integration does support reading files into the bus.

View solution

Q. No processing system (such as an ESB) can deal with a million records at once efficiently.

View solution

Q. Spring Batch reads the file, transforms the records into:-

View solution

Q. The BPM engine would thread together the different actors and work lists,

View solution

Q. You want to expose an interface to clients of your service, without betraying the fact that your service is implemented in terms of messaging middleware.

View solution

Q. Serving to abstract away the functionality of other components in an abbreviated interface to provide courser functionality.

View solution

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