There is no coupling between the client facing interface exposed via t – McqOptions

MCQOPTIONS

1.	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.
A.	True
B.	False
Answer» B. False

Discussion

No Comment Found

Related MCQs

THE_MOST_FUNDAMENTAL_SUPPORT_FOR_GATEWAYS_COMES_FROM_THE_SPRING_INTEGRATION_CLASS:-?$
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.$
The_SimpleMessagingGateway_needs_a_request_and_a_response_channel,_and_it_coordinates_the_rest.$
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.$
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.
The gateway element simply exists to identify the component and the interface.
Messages_sent_on_the_requests_channel_are_forwarded_to_the:-
The capability to hide messaging behind a POJO interface?
Serving to abstract away the functionality of other components in an abbreviated interface to provide courser functionality.
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.