no-rollback-exception-classes element Exception classes that should no – McqOptions

MCQOPTIONS

1.	no-rollback-exception-classes element Exception classes that should not cause the transaction to roll back.
A.	True
B.	False
C.	May be
D.	Can't say
Answer» B. False

Discussion

No Comment Found

Related MCQs

The RetryTemplate supports many use cases, with convenient APIs to wrap.
There’s nothing to prevent you from having many steps within the flow elements.
All errors thrown from Spring Integration components will be a subclass of
Some invocations will fail but may be retried with some likelihood of success in a transactional scenario.
Spring Batch provides a lot of flexibility and guarantees to your application, but it cannot work in a vacuum. To do its work:-
Transaction capabilities are built on top of the first class support already provided by the core Spring framework.
The RetryTemplate itself is configured in the Spring context, although it’s trivial to create in code.
MapJobRegistry instance. This is critical—it is the central store for information regarding a given Job.
Attribute to configure how many items will be processed before the transaction is committed all the input is sent to the writer.
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