Thus, JBI brings WSDL centric
standardization, whereas Mule provides more options in terms of flexibility.
Celtix
Celtix is an ESB which is JBI-compliant. Leveraging Celtix, developers can build
service engines and binding components. Since Celtix is JBI-compliant, the service
engines and binding components too are JBI-compliant, hence can be deployed into
another third-party JBI container. Similarly, Celtix is also a full fledged JBI-compliant
container. This means any third-party JBI-compliant service engines and binding
components can be deployed into a Celtix ESB container.
Even though Celtix is JBI-compliant, JBI objectives are slightly different from that of
Celtix. The main differences are listed as follows:
A JBI-compliant service engine or binding component is essentially a black
box and there is little or no control over the message flow within them.
???
JBI Container??”ServiceMix
[ 64 ]
The normalized message format specified by JBI is XML and hence exchange
of non XML-based message formats, like that of CORBA, will be difficult
and at the very least will require the binary formatted messages to be
transformed into an XML format.
Pages:
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112