Data sheet

Open Source Java Frameworks on HPE NonStop

This document describes HPE support for specific Open Source Java Frameworks to enable development of enterprise Java applications for HPE Integrity NonStop platform.

The open source community has developed many Java frameworks that substantially simplify the task of developing enterprise Java applications. These open source frameworks have been widely adopted by Java developers and, in many cases, have become the de facto technology for developing enterprise Java applications, largely replacing Enterprise JavaBeans (EJB) technology.
In order to provide this open source framework-based environment to developers wishing to design enterprise Java applications for HPE Integrity NonStop servers, specific open source frameworks have been tested and are supported on NonStop. They are:

Spring framework

The Spring framework promotes the development of enterprise Java applications using loosely coupled Java objects known as Plain Old Java Objects (POJOs). Spring framework focuses on the "plumbing" of enterprise applications so that teams can concentrate on application-level business logic, without unnecessary ties to specific deployment environments. The rich set of functionality embedded in the Spring framework provides capabilities that help:
  • Enable loose coupling of POJO objects using a technique known as dependency injection (DI). Using DI, an object can be "wired" to its dependent objects by means of configuration settings without the object having to be hardwired to its dependent objects.
  • Facilitate modularization of code dealing with cross cutting concerns using a technique known as aspect-oriented programming.
  • Provide strong abstractions for working with common Java EE specifications such as JMS, JPA, and JTA.
  • Impart abstractions for various database access technologies such as Java Database Connectivity (JDBC), Hibernate, iBATIS, and so on, making the usage of these data access technologies simpler and less error-prone. These abstractions also make it possible to replace an application's data access objects (DAO) that uses - say, JDBC with DAO objects that uses Hibernate without impacting the rest of the application.