Lomboz concept indicates that J2EE application development is a complete development process. Therefore, it must include all phases of the application development process, such as: encoding, compiling, deployment, testing, commissioning, etc.
A program that complies with the J2EE specification relative to a normal Java program is that the application is deployed in package mode based on the standard component organized by the WEB application and the EJB application, which constitutes an enterprise application.
According to J2EE specifications, these Web and EJB applications have a good definition and standard structure that forms the contents of "Modules" in J2EE applications. For these "Modules", an application server provides and manages the operating environment. An application server can manage many modules at the same time.
"Development Must Be a Reflection of The End Goal, The Production Environment".
An enterprise-class application is made up of many modules, so a work that meets J2EE specifications must be able to operate multiple modules at the same time. These modules will not have different copies they produce.
"Developers Must Not Be Limited With Our Restricted Views of How Things Should Happen".
We often tend to think that our experiences can solve most of the problems encountered by developers. But this is thinking that there is a vulnerability. Because developers should pay attention to many details for each project. We are trying to use Lomboz automation to make these problems can discover early. Developers can observe and modify Lomboz behavior through custom settings.
Here are three ways to add J2EE's characteristics by using Lomboz for your project:
New J2EE Projects: New J2EE project, this option is adapted for you to build a J2EE project, J2EE Engineering Wizard will help you set some of your projects.
New J2EE Module: New J2EE Module, this option is appropriate to add new Web and EJB Module for your already existing projects. The J2EE Module Wizard will create a new module in your project. This option may require additional steps to determine if your Java Build Path (ClassPath) contains the necessary library files.
New Ear Module: This option is suitable for you to pack your J2EE Modules into a document for an application server. Ears is a primary package tool that contains a variety of WEBs and EJB Modules, which can form an application. You can make an EAR file from the Web and EJB Modules you already exist. Similarly, many application servers (such as WebSphere, Orion, Oracle) do not easily recognize independent Web and EJB Modules. For their best way to configure an EAR and use it as the primary deployment unit.
Enabling EXISTING MODULES: This option is available for you have Web and EJB Modules that is not created with Lomboz. You will make them as J2EE's modules by increasing the required Lomboz components and the J2EE specification. This option may require some additional steps to determine if your Java Build Path (ClassPath) contains the necessary library files.
