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

View solution

Q. Spring Integration ships with useful splitters that require no customization.

View solution

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

View solution

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

View solution

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

View solution

Q. For correlation when you might not have a size but know that you’re expecting messages that share a common header value within a known time, Spring Integration provides the HeaderAttributeCorrelationStrategy.

View solution

Q. The only custom logic is a POJO with an @Aggregator annotation on a method expecting a collection of Message objects.

View solution

Q. You want to conditionally move a message through different processes based on some criteria.

View solution

Q. There are some convenient default routers available to fill common needs:-

View solution

Q. To receive messages from an external system and process them using Spring Integration.

View solution

Q. Adapters are opaque in nature.

View solution

Q. Sometimes, functionality is made available from within the application via:-

View solution

Q. You use Spring Integration’s inbound-channel-adapter element to wire the TwitterMessageSource and a poller element.

View solution

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