This section contains the set of considerations to be taken into account
when wrapping the Branch Transformation Toolkit logic into an EJB or Web service.
These considerations provide the application architect or designer with an
understanding of the product's facilities for wrapping toolkit logic. Keep
the following in mind when constructing a solution using EJBs or Web Services:
- Depending on the solution being implemented with the toolkit, encapsulating
the logic in EJBs or Web Services may not provide any benefit in terms of
transactional integrity. This is particularly true when the back-end system
fully provides integrity and the logic implemented in the middle tier is a
pure passthrough. That is, from the client's point of view the middle tier
is acting as the front door of the server logic.
- Irrespective of your model choice, the toolkit provides its full set of
features to build your end-to-end solution. You are free to define the proper
architecture for the application and then use the toolkit to fulfill the requirements
based on the chosen architecture.
- Due to the internal implementation of the toolkit, having more than one
EJB or Web Service implemented by different uncoordinated teams (such as different
vendors) running in the same Java(TM) Virtual Machine and the same namespace
may result in some coexistence problems. Since the use of different namespaces
by different solutions based on the Branch Transformation Toolkit cannot be
always ensured, it is better not to run EJBs or Web Services that have been
implemented using the toolkit in the same JVM with the same namespace. This
can be easily achieved during the deployment of the components, by assigning
the different EJBs or Web Services to different containers (perhaps under
different application server nodes).