Berin Loritsch wrote:
>
> ----- Original Message -----
> From: "Serge Knystautas" <[EMAIL PROTECTED]>
> To: "Java Apache Mail Server" <[EMAIL PROTECTED]>
> Sent: Tuesday, October 10, 2000 2:10 PM
> Subject: Re: Avalon questions
>
> > ----- Original Message -----
> > From: "Berin Loritsch" <[EMAIL PROTECTED]>
> > > I am currently rewriting the configuration engine; however, this is
> > possible.
> > > The current configuration engine blindly builds a simpler DOM like
> > configuration
> > > tree. If you make the <repository> tag so that it is not empty, you will
> > have
> > > child Configuraiton objects.
> > >
> > > Your org.apache.james.AvalonMailRepository will have to be Configurable,
> > and
> > > you simply pass the child Configuration (the whole sub-tree will be
> > passed).
> > >
> > > The new configuration system will have a way to not only type check and
> > validate
> > > your Configuration objects, but prepopulate things like the class
> > attribute
> > > so that the administrator doesn't have to see that--it's the developer's
> > job.
> >
> > I did a little more investigating, and it doesn't seem that what you suggest
> > is possible. The Store component JAMES receives is the class
> > org.apache.avalon.blocks.masterstore.MasterStore. In that class,
> > getPrivateRepository calls instantiateRepository(), which does not support
> > checking for children configurations... just creates the object, calls
> > setAttributes() and setComponentManager() and that's it.
>
> Is that what the MasterStore does? That needs to be changed.
Masterstore doesn't exist in the new Avalon - as far as I can see
The store systems are fairly different from the current ones - so it
won't be a no-brain port.
Charles
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
