> > > // Obtain a reference to a custom mail repository used by this mailet
> > > MailRepository repository = myContext.lookup("myRepository");
> > should be
> > // Obtain a reference to a custom mail repository used by this mailet
> > DirContext repository = myContext.lookup("myRepository");
> > Why would James need a non JNDI interface for Repository ?
> Good point
No, it really isn't a good point. Please think about it. It is actually a
spectacularly bad idea, and I say that as someone who likes JNDI.
JNDI is a directory system, not a message store. Yes, you can store things
as attributes, but you are dealing with JNDI's formats. Yes, you can write
a new SP, but do you really want to try mapping mbox or maildir *AS* a JNDI
context?
JNDI *might* be the right interface for the User Repository, but JNDI is
*not* a replacement for JavaMail. JNDI *is* a good way to get a JavaMail
resource for accessing message content. That ties in with the proposal to
separate the spool from the messsage store, which allows us to use JavaMail
for our message store interface.
Think about this, but let's not get into the details of user and message
repositories just yet. Let's try to finish up the issue of using JNDI as
the means to access resources.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
