Yes, I very much would like to get a major release done soon. The result of
this morning's debugging led me to add saveChanges() during the processing,
and I think I just have to figure out how to work with the new CVS server to
commit. I've also written a "AddFooter" mailet to put a footer on a
message. I'd also like to remove other Town dependencies which are in a few
mailets.
Is there a good way we can define database sources via Avalon? I know
excalibur could do it in theory, but I don't know how. If we could do this,
it would simplify removing these Town dependencies and simplify the
configuration of the repositories.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
----- Original Message -----
From: "Charles Benett" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: "Jakarta-James User" <[EMAIL PROTECTED]>
Sent: Tuesday, July 31, 2001 10:00 AM
Subject: Re: Input for JDB Mail Repository
> Serge Knystautas wrote:
> >
> > Charles,
> >
> > This is a good idea to get feedback, but I've actually taken a stab at
this
> > (<rant>actually I was debugging a freakin' annoying "feature" of
JavaMail...
> > if you set new content on a message, you have to call "saveChanges()"
for it
> > to take effect. what a brilliant design. I think I might change James
so
> > it automatically calls saveChanges after a mailet makes a change as I
think
> > the SMTP Transport engine Sun wrote already is doing this. </rant>).
> >
> > Anyway, here's what I did. If you configure db://conf/spool, this will
look
> > for a configuration file at conf/spool (this should be a file, not a
> > directory). This configuration file contains necessary JDBC connection
> > stuff (driver, URL, username, password), table name, repository name,
all
> > the SQL used by the JDBCMailRepository, and a directory for message
bodies
> > (more later).
> >
> > Right now it's just reading it in as a Properties object (name=value),
but
> > this could be changed to XML (then with includes, you could keep all the
> > JDBC and SQL in one shared XML file, and each conf file would only set
the
> > repository name (and maybe table name). I'm not incredibly pleased with
> > this design as I think I'd rather this all be in the avalon loaded conf
> > files, but what can you do?
> >
> > Two other notes:
> > - I still haven't gotten excalibur (or any JDBC pooler) integrated yet.
> > >From what I've seen of excalibur, it looks like I have to let avalon do
the
> > configuration, so I'm not sure how to back-fit my conf file into an
> > excalibur.
> > - I've written the JDBCMailRepository to store message bodies in the
file
> > system. Even after all this work to not parse messages, a large message
(a
> > meg or more) would still bring my JDBC driver to a crawl. Now, the
> > JDBCMailRepository will store all delivery information and the message's
> > headers to the database, and the message body separately to the file
system.
> > It's hopefully written in such a way that you could turn this off and
on, as
> > it should already read a message that is entirely stored in the database
and
> > so you'd just have to change how it saves messages.
> >
> > Anyway, I was still testing and hadn't committed anything yet. It looks
> > pretty stable, but I thought this morning's error was something
seriously
> > wrong with the parsing-avoidance code.
>
> Great! I'm quite happy to leave it alone if you're making progress.
> My not-so-hidden agenda is to get your dbmail stuff finished and into
> the main tree, update to the latest Avalon stuff (the Avalon Framework
> bits had a full release yesturday) and start thinking about a release of
> James.
>
> Charles
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
