Managed Versus Non-Managed Environments

Last modified on September 24th, 2014 by Joe.

This Hibernate tutorial is to understand the difference between having a managed vs non-management environments. Configuring Hibernate requires us to determine the type of environment that Hibernate is going to function.

Managed and Non-managed are two different types of environments where Hibernate will fit in the architecture comfortably. Both these environments have their own advantage and disadvantages, it depends on the project business requirements and use case. Going through the Hibernate architecture will help to understand this better.

Managed Environment

Managed Environment means that everything Hibernate needs will be handled by the environment itself; transaction and connection pooling are two important things Hibernate will require any compliant JEE server to provide.


Non-Managed Environment

Non-Managed Environment needs us to add some additional efforts by providing Hibernate with all what it needs. Following this tutorial we will see with an example to explain how to can configure Hibernate Framework in a Non-Managed Environments, so no JEE container is required and even no need for Apache Tomcat as well.


Comments on "Managed Versus Non-Managed Environments"

  1. Lochan kumar khuntia says:

    This tutorial really usable and having importance.


  2. Anuj says:

    Good and smartly explained.

Comments are closed for "Managed Versus Non-Managed Environments".