Java Reference
In-Depth Information
• The architecture uses JSF Faces servlet (FrontController),
which is the gateway to all the incoming requests to the
system. It handles the client session at common place in
HttpSession object at the web tier.
• EJB tier is not used for handling the stateful session hence
affecting the application's scalability.
• Most of the application server supports HTTP session in
memory replication and will be used during the applications
clustered failover.
Transaction & Concurrency
The following mechanisms were recommended for Zamco
Application architecture for transaction & Concurrency
•
The
application
design
incorporates
container-managed
transaction
for
database
transactions,
which
allows
for
simpler, more portable code.
• All transactions related to one component are managed by a
single workflow manager object through an EJB. This EJB is
a stateless session bean designed using the facade pattern.
• The architecture uses JPA Entity (Payment (@Entity)) to
handle the payment transaction. The method is invoked with
Requires New transaction attribute set via a stateless session
bean.
• Entity instance are based on rows and EntityManager takes
care of concurrency.
