PEtALS

Table of Contents

1. Building PEtALS from source
1.1. Pre-Requisites
1.2. Checkout the sources
1.3. Compiling PEtALS modules
1.4. Assembling PEtALS modules
1.4.1. Standalone server
1.4.2. Component framework
1.4.3. Web application
1.4.3.1. JONAS
1.4.3.2. JBOSS
1.4.3.3. SIMPLE WEB APPLICATION
1.5. Compiling PEtALS Eclipse Plugins
2. PEtALS Coding Rules
2.1. Formatting rules
2.2. Naming conventions
2.2.1. JBI artifacts
2.2.1.1. Components
2.2.1.2. Service units, assemblies and shared libraries
2.3. How to ...
2.3.1. How to escape a warning detected by Findbugs
3. Developing under Eclipse
3.1. Tools and plugins
3.2. Preparing eclipse
3.2.1. Multiple workspaces
3.2.2. Maven classpath variables
3.2.3. Selecting the JDK and its options
3.2.4. Multiple workspaces building
3.2.5. Use the good source code formatter
3.2.6. Use the good configuration of the source code reviewer tools
3.2.6.1. Configuration of PMD
3.2.6.2. Configuration of Checkstyle
3.2.6.3. Configuration of Findbugs
3.3. Working on PEtALS projects
3.3.1. Importing project
3.3.2. Create a PEtALS launcher
4. Using maven
4.1. Creating a new module
4.2. Creating new projects
4.2.1. Creating a Binding Component
4.2.2. Creating a Service Engine
4.2.3. Creating a service unit
4.2.4. Creating a service assembly
4.3. Deploying artefacts to repositories
4.3.1. Deploying a POM
4.3.2. Deploying a JAR
4.3.3. Deploying a source JAR
5. Releasing PEtALS
5.1. Releasing a module
5.1.1. Preparing the release
5.1.2. Performing the release
5.2. Releasing a POM file
5.3. Maintenance Release
6. Remote debugging with PEtALS
6.1. Debuging with Eclipse
6.1.1. Run PEtALS
6.1.2. Attach Eclipse IDE to PEtALS
7. Profiling with PEtALS
7.1. Profiling with NetBeans
7.1.1. Profiler Agent installation
7.1.2. Run PEtALS
7.1.3. Attach NetBeans IDE to PEtALS
8. Best practices
8.1. Managing bugs and feature requests
8.1.1. Bugs
8.1.2. Features