Eclipse Virgo GreenPages Demo

Changes

26-Apr-12
- Properties externalized for database connection - see solution/etc/properties directory
- Created plan file for deployment - see solution/etc/plan directory
- Refactored directory greenpages.app to greenpages.services
greenpages-parent-solution pom.xml
Spring version 3.0.7 and surefire plugin to use corresponding spring instrument version
Dependencies versions specified in dependencyManagement section
Fixed Bundlor configuration
Corrected inconsistencies between template.mf files
Builds in Maven 3
Tested in Virgo 3.0.2.RELEASE
Does not work in 3.5.0.M3 - unable to find database driver!

Virgo Dependencies
- Created Spring 3.0.7 libd file
- Added instrument jar to libd file (not sure if necessary)
- Replaced Spring 3.0.5 jars with 3.0.7 in $VWS_HOME/repository/ext
Virgo Files
- $VWS_HOME/configuration/org.eclipse.virgo.kernel.userregion.properties

When changing dependencies, ONLY change the template.mf file, Maven Bundlor plugin will automatically generate the correct MANIFEST.MF file
Updating Application version should be done in all pom.xml and template.mf files

Database Location: $USER_HOME/greenpages-db/greenpages
Driver JAR: - $USER_HOME/.m2/repository/com/h2database/com.springsource.org.h2/1.0.71/com.springsource.org.h2-1.0.71.jar
Driver URL: - jdbc:h2:~/greenpages-db/greenpages
Port: 9092
Userid: greenpages
Password: pass
Driver Classname: org.h2.Driver

$ mvn clean package

Copy services, db, jpa and web jar/war files (declared in the plan file) to $VWS_HOME/repository/usr directory
Copy *.property files from etc/properties directory to $VWS_HOME/repository/usr directory
Copy etc/plans/greenpages.solution.plan to $VWS_HOME/pickup directory

Copy the solution/target/greenpages*.par to $VWS_HOME/pickup directory
Copy the solution/target/par-provided/*.jar to $VWS_HOME/repository/usr directory

Virgo's Bundlor uses the template.mf file to create the manifest in target/classes/META-INF/MANIFEST.MF
IMPORTANT - The Maven war configuration MUST reference the generated MANIFEST and ignore the one in src/main/webapp/WEB-INF/
Added Bundle-Description to the template.mf and MANIFEST.MF files. Once the packaging is done, the resulting packaged MANIFEST.MF files should be have been generated by the Bundlor.
Changed Bundlor to run in the "process-classes" phase to ensure it is done before packaging to avoid inadvertant overwriting by the static MANIFEST.MF file.