Jump to: navigation, search

OFMP/Release 1.0.0M1


  1. Oracle XE 10.2 with system/system credentials
  2. JDK 1.5 (not JRE as Maven requires a JDK)
  3. Spring Tool Suite 2.3.1
  4. Subversive Plugin
  5. Subversive/M2Eclipse integration

SCM access

See http://code.google.com/p/ofmp/source/checkout

Build Source

  1. Ensure the default JRE in Eclipse Preferences -> Java -> Installed JREs is of version JDK5.x.y.z
  2. At this stage OracleXE must be up and running
  3. Create an Eclipse Workspace in C:\dev\ofmp
  4. In SVN Repository view, browse to the ofmp project
  5. Right click -> Checkout as Maven project... -> Choose HEAD
  6. Let m2eclipse checkout and compile all the modules (ignore popup errors) => Might take 15 minutes if new Maven local repo
  7. When done, close all modules except the "ofmp" module
  8. Run "mvn clean install" on the "ofmp" module => Might take 10 minutes if new Maven local repo

Datamodel will be setup in the same process

In future runs, if you dont want datamodel to be reset:

mvn -Dno_database_setup=true clean install

The Eclipse Target is built during the installation process as well with the core-runtime module.

  1. Go to Window -> Preferences -> Plugin Development -> Target
  2. In predefined Targets, load \org.eclipse.ofmp\runtime\server\core-runtime\org.eclipse.ofmp.server.core.target

To have a clearer view of your Eclipse workspace, import /ofmp/workingSets.psf Project Set file and choose Working Sets as Top Level elements in your Package Explorer. All workspace projects must be opened for this operation to work.

Then close all projects in the "dependencies" working set.

Known Building issues


Bundles org.eclipse.ofmp.datasource.oracle and org.eclipse.ofmp.transaction wont compile due to the org.eclipse.ofmp.lib.jencks bundle project config.

Open the org.eclipse.ofmp.lib.jencks project, add all the JARs in the lib folder to the project's build path, go to Project -> Properties -> Java Build Path -> Order and Export, check all the JARs in the lib folder.

Edit org.eclipse.ofmp.datasource.oracle and org.eclipse.ofmp.transaction Manifest files, save them back.

Refresh org.eclipse.ofmp.common Manifest file

Spring file editor issues

  • The file org.eclipse.ofmp.datasource.oracle\META-INF\spring\ds-context.xml will contain an error. (to be ignored)

OFMP bundles creation

For every service to be extracted from the org.eclipse.ofmp.service.core project we have to:

  • extract bundle (scr and src.tests) from the core, mavenize and OSGify it
  • create an integration test project based on Spring DM test framework and run integration tests on it.


  • Right click on \org.eclipse.ofmp\core\bundles and create a new Maven module using New -> Other -> Maven -> Maven Module
  • Create the module using the spring-osgi-bundle-archetype
  • Create an integrationtests Maven module if required in \org.eclipse.ofmp\core\integration-tests
  • Setup pom.xml (org.eclipse.ofmp.security/pom.xml is a good example)
  • Rename packages to org.eclipse.ofmp (dont use "service" prefix for bundles)
  • Use Bnd to automate generation of Manifest.MF OSGi tags:
    • replace Require-Bundle by Import-Packages as much as possible
    • ensure proper bundles versioning AND dependencies versioning e.g.: Import-Package: osgitut.movies;version="[1.0.0,2.0.0)"
    • Hide Implementation Details: ONLY export public API packages in Manifest

Put implementation details in separate packages from the public API

org.example.foo - exported API package
org.example.foo.internal - private implementation package
  • Remove any specific wordings (victoria/apsys) in source code
  • Enable project Spring nature if required and enlist Spring files in project properties

Naming conventions

  1. every service bundle does not hold the ".service." acronym in its bundle name
  2. every lib bundle(like Jencks) should contain the ".lib." acronym in its bundle name

Integration Tests infrastructure

OFMP Test infrastructure is built on Spring DM Test framework

Have a look at

  • org.eclipse.ofmp.test/src/main/java/org/eclipse/ofmp/test/AbstractOFMPDBUnitTest
  • org.eclipse.ofmp.test/src/main/java/org/eclipse/ofmp/test/AbstractOFMSpringDMTest

The org.eclipse.ofmp.test bundle expose the service required to cleanup/initialize the database before any tests.

See for instance org.eclipse.ofmp.currency.integrationtests\launch\AllCurrencyTests.launch

Open tasks

  • Load time weaving of aspects using Equinox Aspect and Spring AOP. needed for some iBatis handlers.
  • Remoting/Web infrastructure
  • BIRT integration
  • Replace OracleXE with Apache Derby
  • Add File headers using proper tool

Backend bundles

  • org.eclipse.ofmp.common (done)
  • org.eclipse.ofmp.datasource.derby
  • org.eclipse.ofmp.datasource.oracle (done)
  • org.eclipse.ofmp.transaction (done)
  • org.eclipse.ofmp.mail
  • org.eclipse.ofmp.security (done)
  • org.eclipse.ofmp.currency (done)
  • org.eclipse.ofmp.date
  • org.eclipse.ofmp.calendar
  • org.eclipse.ofmp.counterparty
  • org.eclipse.ofmp.deal
  • org.eclipse.ofmp.history
  • org.eclipse.ofmp.users
  • org.eclipse.ofmp.reporting

UI Bundles

  • org.eclipse.ofmp.common (done)
  • org.eclipse.ofmp.ui.users
  • org.eclipse.ofmp.ui.deals
  • org.eclipse.ofmp.ui.history
  • org.eclipse.ofmp.ui.reporting

Know Issues


  • Be patient, drink coffee or beers. On first OFMP installation, setting up your local Maven repository might take 30 minutes.
  • Always keep number of opened projects as low as possible
  • MANIFEST.MF files do not always refresh properly after BND generation, open and press F5.



Eclipse Procedures et Legal docs