james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harmeet Bedi" <harm...@kodemuse.com>
Subject Re: Avalon dependance in mailets
Date Mon, 06 Jan 2003 16:51:32 GMT
How about
getMailetContext().getUserRepository(Object name)

instead of
getMailetContext().getUserRepository(String name)


----- Original Message -----
From: "Danny Angus" <danny@apache.org>
To: "James Developers List" <james-dev@jakarta.apache.org>
Sent: Monday, January 06, 2003 5:40 AM
Subject: RE: Avalon dependance in mailets

> Hi,
> My next step is a little less clear, and requires some decision making,
> I'm going to do the same thing for user repositories, so that
> getMailetContext().getUserRepository(String name)
> returns a UserRepository, however I don't like the incosistency between
> specifications for MailRepositories and names for UserRepositories.
> We need, IMO, to select one style and use it consistently, I favour URL's,
> which allow repositories to be created dynamically by mailets without
> config changes, but what are the other opinions? Technnically its not a
> issue but in order to ensure portability of mailets, the primary objective
> of the excercise, we need to document what the string can contain.
> I'm going to implement getMailetContext().getUserRepository(String name)
> the basis that it doesn't break existing configurations, and changing it
> getMailetContext().getUserRepository(String URL) later is not really a
> change to the method signature, but an implementation detail.
> > -----Original Message-----
> > From: Danny Angus [mailto:danny@apache.org]
> > I've started commiting changes I've made which remove avalon
> > dependance from
> > the standard mailets.
> > Starting with repository access,
> --
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:   <mailto:james-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@jakarta.apache.org>

View raw message