On 20/12/2007, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote:
> On Dec 12, 2007 5:33 PM, Bernd Fondermann <[EMAIL PROTECTED]> wrote:
<snip/>
> > > I could just use some pointers on how to dynamically register a new Mailet
> > > onto a JAMES server via Java code if thats possible. e.g. I was thinking a
> > > Camel consumer, from("james:localhost"), could essentially create a Mailet
> > > and register itself?
> >
> > AFAIK, mailets are only loaded at app initialisation time and are static
> > from thereon. This is done by putting a jar on the classpath.
> >
> > see http://wiki.apache.org/james/CustomMailetPackages
>
> i think a component-centric packaging format for mailets allowing hot
> deployment would be good. perhaps just a jar with additional meta-data
> in META-INF would be good enough.
>
I'd like to see hot deployment too, what kind of meta-data did you
have in mind? Some things are obvious like the mailet class and the
pipeline name to place it in. But how would you establish the order of
a processor pipeline? I see two simple options: either use a numeric
attribute like servlets, and trust the mailet deployer knows enough
about the current config to get it in the right place or use a
exec-after attribute to say what must have already executed.
Are these approaches too simplistic? I can imagine both causing
non-deterministic order but perhaps leaving the configurer to resolve
such issues is ok? Especially if combined with an MBean to report and
modify the order?
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
