Prev | Current Page 81 | Next

Binildas A Christudas

"Service-Oriented Java Business Integration"


2. Provider: Provider then publishes the service description in WSDL format.
3. Consumer: Consumer then discovers the required service. This can happen at
design time (static binding) or run time (dynamic binding).
4. Consumer: Invokes the queried service.
5. Provider and Consumer: Send and respond to message exchanges according to
the MEP, and state of the message exchange instance.
6. Provider: Provides the service by responding to the function invocations.
7. Provider and Consumer: Responds with status (fault or done) to complete the
message exchange.
During run-time activation, a service provider activates the actual services it
provides, making them known to the NMR. It can now route service invocations to
that service.
javax.jbi.component.ComponentContext context ;
// Initialized via. AOP
javax.jbi.messaging.DeliveryChannel channel = context.
getDeliveryChannel();
javax.jbi.servicedesc.ServiceEndpoint serviceEndpoint = null;
if (service != null && endpoint != null)
{
serviceEndpoint = context.activateEndpoint
(service, endpoint);
}
The Provider creates a WSDL described service available through an endpoint.


Pages:
69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93