Container Services
Container Services
develop these services yourself, you are free to concentrate on solving the business problem at
hand.
functionality that supports the component. Before a web, enterprise bean, or application client
component can be executed, it must be assembled into a Java EE module and deployed into its
container.
application and for the Java EE application itself. Container settings customize the underlying
support provided by the Java EE server, including services such as security, transaction
management, Java Naming and Directory Interface
system resources are accessed only by authorized users.
single transaction so that all methods in one transaction are treated as a single unit.
in the enterprise so that application components can access these services.
and enterprise beans. After an enterprise bean is created, a client invokes methods on it as if
it were in the same virtual machine.
the same Java EE application can behave differently based on where they are deployed. For
example, an enterprise bean can have security settings that allow it a certain level of access to
database data in one production environment and another level of database access in another
production environment.
cycles, database connection resource pooling, data persistence, and access to the Java EE
platform APIs (see
illustrated in