As I said in my response to Andrew's email of 7/7, I am just beginning to
investigate JAMES. I have the code and I am trying to get through it. I have
also looked through the Avalon and JAMES doc (such as it is). Realizing I
probably don't see the big picture yet, please correct any
misunderstandings. And if this is all totally obvious, please tell me.
I kept Andrew's 7/7 email and waited for someone to reply with a "JAMES
already stores email in a DBMS". I didn't see one. It seems like a good idea
to do this. My original thinking was that the interface to the DBMS would be
in a Mailet. This way it could be configured in or out of the processing
pipe-line by the user. And a single email (or parts thereof) could possibly
wind up in multiple places.
Reading the configuration.html that came with my JAMES package (1_0b2),
there is already a ToRepository mailet. Is this an ObjectStore? Does it use
an ObjectStore?
The repositoryPath in the example is an URL for a file system location. Is
it reasonable to assume that this URL could be a JDBC connect string? Is
that what you (Serge) meant by "ObjectStore ... in a database"?
It seems to me that there ought to be functionality for multiple, named,
ObjectStores (perhaps there already is). Traditional inboxes and
database-based inboxes could supported at the same time. And if the
ObjectStore interface is generic enough, it won't matter if there is a file
system, RDBMS, or ODBMS (or all 3) hiding behind it.
Bill
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Serge Knystautas
> Sent: Wednesday, July 12, 2000 10:06 AM
> To: Java Apache Mail Server
> Subject: Re: Extending Mail/Stream Store with Relation Database Layer
>
>
> I started to respond to <<SNIP>>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/>
Problems?: [EMAIL PROTECTED]
