This is similar to JBI binding of services providing a mediation layer for service
integration, more of which we will see in later chapters.
We now have had enough of traditional bindings and bindings using XFire. With
this background it is time now to delve deep into JBI and related services. We will
continue with more JBI discussions in the next chapter by understanding the JBI
packaging and deployment model.
JBI Packaging and
Deployment
Small things matter; whether packaging and deployment are smaller concerns
compared to design and development, is still under dispute. However, one thing is
clear, that a standard way of packaging and deployment promotes cross-platform
and cross-vendor portability of components, whether it is our familiar .jar, .war,
and .rar files or the new JBI archive defined by the JBI specification.
ServiceMix is a container for JBI components. At the same time the ServiceMix
JBI container by itself is a JBI component. This characteristic enables ServiceMix
to be deployed as a standard JBI component into another vendor's ESB container,
provided the host ESB container supports JBI components.
Pages:
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185