Using Kettle in other contexts then Engage
Michelle
michelle.dsouza at utoronto.ca
Tue Dec 1 18:49:56 UTC 2009
Hi,
At the Infusion code sprint we spent a little time talking about using Kettle in contexts other then Engage. This conversation came out of the need of both Decapod and the bug parade component to use Kettle.
Some of the goals for this work are:
1. the ability to create and deploy self contained WAR files easily
2. developers should be able to work in eclipse with jetty where the file structure is slightly different then in the deployed WAR
3. developers outside the Fluid community should also be able to easily use Kettle if they want to
To accomplish this we need to:
1. Split out Kettle specific code from Engage specific code
2. Write code to load the application from a configurable directory
3. Create a generic deploy script which could read from a configuration file and move dependencies into the application directory
With this strategy we are making the following assumptions:
1. Each instance of Kettle will have a single application. This implies that on the Fluid build site we would deploy three instances of Kettle - one for Engage, one for Decapod and one for the bug parade component.
2. We would have an application loader configuration file that would specify where the application was located. This would allow for different structures in our working environments and in the deployed WAR.
3. The application directory would either contain all its dependencies or the the dependencies would be moved to the correct place by the deploy script. In this case we would require an alternate configuration file to address path changes.
I'm currently starting on this work and I hope to have something committed soon for you to look at. I'm going to work in the ENGAGE-208 branch that I created yesterday.
Michelle
------------------------------------------------------
Michelle D'Souza
Software Developer, Fluid Project
Adaptive Technology Resource Centre
University of Toronto
More information about the fluid-work
mailing list