Gazelle Developers Guide
Gazelle Developers Guide
Introduction
This wiki describes how a new developer would get started in the Gazelle project.
Not all terms used in this document will be defined in this document. If you are unfamiliar with some of the terms, you will need to request help.
Prerequisites - Development Tools
Different development tools are available on Prerequisites - Developement Tools.
Code Control - Access to the Forge
Source code is checked in into Forge. You will need to control code to develop your Gazelle application. See on Code control.
What is a Gazelle Web application ?
You need to develop in a module inside a Gazelle application, you need to create a Gazelle frinnedly application or you want to know about architectures of our applications. We detailed things to know on this page.
Develop a Gazelle Web application in a JBoss environment
The purpose of this section : detail how to develop a Gazelle web application in JBoss environment. We create this document as a help - guide for new Gazelle developers to start their web application works in a JBoss environment and to explain how to develop.
This chapter is a How-To way to answer to your questions, and is also an important prerequisite before starting your development.
It details :
- 1. How to configure your Eclipse environment ?
- 2. How to install an existing Gazelle Web application, and work safely on it ?
- 3. How to create a new Gazelle Web application ?
- 4. How to create a new module in your Gazelle Web application ?
- 5. How to import an existing module into existing project (application) ?
- 6. How to start to develop your EJB3-JSF in your project ?
- 7. How to generate EJB3-JSF from an existing database ?
- 8. Open issues
A new developer should normally follow steps detailed in #1, then #2 or #3-4, then #6.
How to configure your Eclipse environment ?
See How to configure your Eclipse environment ?
How to install an existing Gazelle Web application, and work safely on it ?
See How to install an existing Gazelle Web application, and work safely on it ?
How to create a new Gazelle Web application ?
See How to create a new Gazelle Web application ?
How to create a new module in your Gazelle Web application ?
See How to create a new module in your Gazelle Web application ?
How to import an existing module into existing project ?
See How to import an existing module into existing project (application) ?
How to start to develop your EJB3-JSF in your project ?
See How to start to develop your EJB3-JSF in your project ?
How to generate EJB3-JSF from an existing database ?
See How to generate EJB3-JSF from an existing database ?
Open issues
- Add a Javadoc section, explaining how to syntax it in our application, and how to use it
- Add a TestNG section, to describe how to develop and perform our unit tests
- Add a Design section, describing our graphical chart and associated codes to use in our GUI modules
Compile/Deploy Times
This section lists the time it takes to start the JBoss server from scratch with the Test Management application on various platforms. The goal is to help developers understand what to expect for debug cycles.
| Location | User | Environment | Development/Production | Build time | JBoss Startup | JBoss Deployment | Comments |
|---|---|---|---|---|---|---|---|
| ERL | SMM | gazelle-gold, Debian VM on | Development | 10 s | x s | 60 s | NA |
| ERL | Jarek, is this you? (No, that's not me.) The Precision 690 is a workstation in my office, not one of your VMs. | Dell Precision 690, 3 GB, 2 GHz, CentOS 5; build by hand, not in Eclipse | Development | 14-31 s | 110 s | 110 s | Need to restart JBoss for each build to avoid permgen error |
| ERL | Dell Latitude D600 Laptop, 2 GB, 2 GHz, XP; build by hand, not in Eclipse | Development (Really Gazelle Master Model, need to retest with Test Management) | 65 s | 90 s | |||
| ERL | JK | Dell Latitude C840 Laptop, 650 MB, 1.2 GHz, Fedora 8; Ant build in Eclipse, JBoss started in Eclipse | Development | 21s - 35s | 79 s | What is menat by JBoss Deployment? Redeplyment on a running server? | Need to restart JBoss for two deployments to avoid permgen error |
| ERL | SASI | Dell Optiplex GX620 desktop. CPU: Intel Pentium dual core CPU 3.00GHz. Memory: 3.6 GB OS: Fedora 5 build Both Ant/JBoss run from within Eclipse |
Development | 12s (TM) | 54s (TM) | N/A | |
| INRIA | JRC | Dell Latitude D620 Laptop, 2 GB +2 GB swap, 2 GHz, Kubuntu 8.10 (kernel 2.6.27 -kde 4.1); Ant build by hand, JBoss started by hand | Development (PR/TM/GM) | 9 s (TM) | 44 s (with TM) | 15 s (TM) | I work only with one project within JBoss to win time (I remove others not used EAR/JAR projects/examples (TM or PR or GM) from /deploy) |
| INRIA | JBM | Mac Book Pro, 2 GB, 2x2.6 GHz, Mac Os X 10.5.6 ; Ant build by hand, JBoss started by hand | Development ( TM ) | 19 s (TM) | 38s:275ms (with TM) | 27.292s (TM-dev the import sql take a long time) | I work only with one project within JBoss to win time (I remove others not used EAR/JAR projects/examples (TM or PR or GM) from /deploy)
} |