Re: Process configuration store

[Matthieu Riou <ma...@gmail.com>]

Hi,

I've just committed that stuff. Hopefully I haven't broken anything. I've
runned simple deployment scenarios and some of the test we have (subliminal
message: thanks Lance) and things seem to work properly. But let me know if
you run into some weird behavior.

Cheers,

Matthieu

On 10/24/06, Matthieu Riou <ma...@gmail.com> wrote:
>
> Hi,
>
> I'm going to do some refactoring on the way we store processes and
> processes information. Right now the ProcessDAO is a mix of both
> configuration information (deploy date, custom properties, active/retired,
> serialized compiled process) and runtime information (instances,
> correlators) which isn't so nice. It's also the source of many deployment
> problems as we have some duplicate information between the filesystem (the
> deployed process bundles) and the database.
>
> To clean that up I'm going to introduce some sort of process configuration
> store (still haven't found a really impressive name for it). It would handle
> process deployment, maintaining these deployments over time (which involves
> redeployment or undeployment but could also be versioning in the future) and
> configuration changes. The runtime would use it to get information about
> processes currently deployed to activate them.
>
> That would both introduce a cleaner separation between runtime and static
> process definitions and would be much more in line with the deployment
> specifications. It would also make clustering easier as configuration could
> be easily propagated.
>
> Comments or shouts of excitation are welcome.
>
> Matthieu
>