This project presents a sample app for aggregating and re-presenting horoscopes. It is designed to highlight a number of areas for discussion that are usually overlooked. These include:

• various levels of testing, and their general appropriateness ranging from simple unit tests to integration tests
  • how to get integration tests playing nicely within a shared build environment - loads of developers, a CI server
  • a couple of different ways of testing a Camel route
    • using the standard CamelSpringTestSupport approach with mock: and direct: endpoints
    • exercising an actual component against an embedded web server (assigned to a unique port)
  • writing routes in such a way that they can be easily tested
• setting up MyBatis for data access across OSGi bundles that actively demonstrates the mybatis and mybatis-spring documentation, with
  • Spring transaction management for camel-mybatis
  • configuration externalised using the OSGi Config Admin mechanisms (property files in the $FUSE_HOME/etc directory)
  • testing the correctness of data access against an embedded H2 database (contentious and potentially not applicable to all your access needs)
• reuse of expensive resources such as DataSources between disparate bundles through the use of service references
• configuration of database drivers and connection pools (c3p0) in an OSGi environment

The Maven projects contained within are as follows:

• horo-model - Basic model used by the application
• horo-db - Database access; exposes both a DataSource and a Camel Mybatis component for reuse
• horo-rss-reader - Initial endpoints for consuming RSS feeds
• horo-web - REST endpoints that present a view into the database

All of the above ws- bundles are based on Spring DM.

There are three additional parent projects that simplify the Maven project configuration:

• bundle-parent - used as parent by all bundles
• camel-bundle-parent - used as parent by all bundles
• horo-features - Contains an XML features file used to install the rest of the bundles.

1. This project has been designed against JBoss Fuse 6.2.0 (https://access.redhat.com/jbossnetwork/ - registration required)
2. The database backend requires an instance of Postgres 9.1, though older versions may work fine - all SQL has been written to the SQL92 standard. pgAdmin is a great little tool for doing this all visually if you aren't familiar with, or just can't be bothered using, the Postgres command line. To set up the project backend you will need to:
   1. create a database instance called horo-db on the local server
   2. connect to the database and run in horo-db/src/main/resources/sql/schema.sql
   3. run in horo-db/src/main/resources/sql/postgres-permissions.sql, this will create a login role called horo-app with the password horo-pwd (you can change this later) and set all the appropriate table permissions

1. Build this project so bundles are deployed into your local maven repo

   $ mvn clean install

2. Start JBoss Fuse

   $ bin/fuse

3. Add this projects features.xml config to Fuse from the Console (makes it easier to install bundles with all required dependencies)

   JBossFuse:karaf@root> features:addUrl mvn:com.fusesource.examples/horo-features/1.0-SNAPSHOT/xml/features

4. Install the project.

   JBossFuse:karaf@root> features:install horo-model JBossFuse:karaf@root> features:install horo-db JBossFuse:karaf@root> features:install horo-rss-reader JBossFuse:karaf@root> features:install horo-web

   or you can install them al with the feature 'horo-all'

   JBossFuse:karaf@root> features:install horo-all

5. To see what happened look at the JBoss Fuse log file, either from the console

   JBossFuse:karaf@root> log:display

   or from the command line

   $ tail -f data/log/fuse.log

6. To test the WS, you can use your browser and go to the horoscope service

• http://localhost:8021/rest/horoscopes/signs/{horoscope sign name} (ex: http://localhost:8021/rest/horoscopes/signs/aries)