EJB 3.0 Best Practices for developing deployments on was V7

Introduction

IBM WebSphere Application Server officially supports EJB 3.0 from version 7.0 (in the previous 6.1 release of the feature package for EJB 3.0). EJB 3.0 applications that are currently built on the was V7 are not common. In the actual project, the author summarizes some of the problems (partly development details) and best practices that have been encountered in deploying EJB 3.0 applications using was V7, and attempts to demonstrate these experiences to developers who need to develop EJB 3.0 applications in the was V7 environment with a few simple examples.

This article is based on the following conditions:

Using IBM WebSphere Application Server V7.0 (was V7) as an application server

Development work using IBM Rational application Developer for WebSphere Software V7.5

Some best practices for creating projects

interface, business objects are separated from implementation logic:

It is recommended that the EJB client and all defined business objects (Business Objects) be placed in a project that resembles a dependency library so that it can be easily invoked in other projects in the future. In addition, this improves the maintainability of interfaces and business objects. So when we created the project we chose the "Create an EJB client JAR module to hold the client interfaces and classes" option (so that the client that was automatically generated by RAD would be placed in the client project, and in the future I You can also place custom business objects in the project.

Figure 1. Creating a client JAR module