Danny Angus ha scritto:
I agree with noel, processors should be the deployable application
I'm not sure I understand yours and Noel idea. Noel's message seems to
say that I proposed to redeploy single mailets, instead I proposed to
redeploy the spoolmanager.
Being able to undeploy and redeploy the spoolmanager then you can alter
the configuration of each mailet and each processor.
In the current architecture if you don't unload the spoolmanager you
can't undeploy the mailet/matcher loader and this mean you cannot
upgrade your mailets or add new mailets. Processors and Mailets are not
components in our COP, SpoolManager is instead a component.
Btw, this discussion is not so important. Once we'll have some mean to
redeploy components we will discuss what is the best granularity.
Stefano
On 2/5/08, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
Stefano Bagnara wrote:
The really cool thing would be to have each top level component deployable
as separate osgi bundle, so to be able to undeploy the spool manager,
alter mailet configuration, deploy it back (and other similar things).
Mailet configuration seems the wrong place. Pipeline configuration means
configuring processors, which could be the deployable unit. Processors are
the containers for Mailets. Can you make the argument for why Mailets,
themselves, should not be kept simple and far far away from this stuff?
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
