Index Changes

Provider - Architecture

Jbi4Corba, when run in provider mode, is based on this simple pseudo equation: idl2java + java2wsdl = idl2wsdl.

From the architectural point of view, we analyze two different phases: the deploy and the runtime.


At deploy time the following sequence of events occurs:

  1. The IDL file is parsed and used to generate java classes. (To verify which IDL's features are supported please visit the page of the supported IDL data types.
  2. Generated java classes are compiled.
  3. One JBI web service per idl inerface is created.
  4. When the endpoint is activated the underlying corba object is located using the Corba name service.
  5. Each JBI Web service is published as an internal JBI endpoint.
The following (unformal) sequence diagram shows this process:
The deploy time process.


At runtime the following sequence of events occurs:

  1. The JBI internal endpot is called by another JBI endpoint.
  2. The CXF dynamic interface and the Corba dynamic interface are used together to forward any port called on the web service to the corresponding corba method.
  3. The result is marshalled into the reply payload.
  4. The reply payload is posted into the JBI bus.

The following figure shows this process in an unformal sequence diagram:

The runtime process.

JSPWiki v2.4.100
« Home Index Changes Prefs
This page (revision-6) was last changed on 29-Jun-09 03:23 AM, -0700 by