Using Kettle in other contexts then Engage

[Steven Githens]

Hi Michelle,

This is great and needed stuff.  In the meantime, is there a wiki page 
or README that details how to start up a current engage demo/project?  
I've been trying to figure it out in some bits of free time I've had in 
the last week, but haven't gotten a working war file yet.  I've checked 
out fluid-all and was trying to build a random combination of maven targets.

Also, this may fit in below, but it would be good to have a library that 
comes out of this as well for use in existing applications that will 
various combinations of (template | component tree | rhino script ) and 
produce the output.  So if you're in a situation where you aren't 
nesessaryily using a kettle servlet/full framework, you can still get 
your stuff.  This would be great since fluid is being used in a number 
of projects.  And I like the idea of still being able to serve normal 
webpages with my fluid templates in addition to dynamic stuff... but in 
an existing project. 

This might end up just being the same small library that contains the 
entire kettle|servlet framework and you could just use it in another 
application as well.

Cheers,
Steve

P.S. Complete tangent, but has anyone brainstormed about rendering 
output when you don't have a finished component tree, and may never have 
one. With support for Comet and other mass-port streaming connection 
type things in Java6+ (or some version), it would be interesting if 
there was a component type, like for a branch component which could take 
a sort of generator function and it would just continue streaming output 
until that function ended and moved on.

Michelle wrote:
> 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
>
>
>
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work
>