cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Fagerstrom <>
Subject Re: Real blocks - current state and next steps
Date Mon, 12 Sep 2005 07:55:02 GMT
Reinhard Poetz wrote:

> Daniel Fagerstrom wrote:
>> Deployement
>> -----------
>> During development it is easiest to deploy block by using an 
>> (possibly graphical) OSGi console. Is this ok for production systems, 
>> should we have some web gui?
> A graphical installer is fine for development but IMHO not for 
> production. I need a reproducible state of a system.
> Suppose you have a cluster of 5 app servers running Cocoon. I don't 
> want to connect to every server and install/uninstall blocks there. 
> This is way to error-prone.

Agree. This can still be done using the OSGi configuration service as it 
just is a API, we could have an implementation that take an XML or a set 
of XML files that describes the deployment.

> What I think is some kind of block-installation descriptor[1]. I think 
> M2 will help us here but I haven't had a closer look how this could be 
> done.

Yes, something like that. I'm not up to speed yet with M2, so I don't 
know how we could use M2 here.


View raw message