Service consumers employ one or more service invocation
patterns. Service invocation through a JBI infrastructure is based on a 'pull' model,
where a component accepts message exchange instances when it is ready. Thus,
once a message exchange instance is created, it is sent back and forth between the
two participating components, and this continues till the status of the message
exchange instance is either set to 'done' or 'error', and sent one last time between
the two components.
Message Exchange Patterns (MEP)
Service consumers interact with service providers for message exchange employing
one or more service invocation patterns. The MEP defines the names, sequence, and
cardinality of messages in an exchange. There are many service invocation patterns,
and, from a JBI perspective, any JBI-compliant ESB implementation must support the
following four service invocations:
One-Way: Service consumer issues a request to the service provider. No
error (fault) path is provided.
Reliable One-Way: Service consumer issues a request to the service provider.
Provider may respond with a fault if it fails to process the request.
Pages:
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95