Ah, that sounds pretty interesting. How are you going to structure that?
James runs within Avalon, so I'm not sure how you could get it to act like
an EJB client.
To do this though, you really only need to make your own implementation of
Mail/SpoolRepository, like the Avalon and JDBC ones there now. You have to
define the repository (handles retrieving, locking, listing, storing, etc..)
and the messagesource (defines how to open an input stream to the message
body).
Then you'd change the server.xml (?) to define the new kind of repository
like ejb:// (instead of file:// or db://). Does that give you enough to go
in the right direction?
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
----- Original Message -----
From: "Christoph Sturm" <[EMAIL PROTECTED]>
To: "Serge Knystautas" <[EMAIL PROTECTED]>
Sent: Wednesday, August 08, 2001 1:57 PM
Subject: Re[2]: EJB Messagestore
> Hello Serge,
>
> Wednesday, August 08, 2001, 4:42:27 PM, you wrote:
>
> SK> Well, Avalon/James isn't an EJB server, so I don't know if/why you
need to
> SK> modify James... seems like you would just build Entity beans (BMP or
CMP)
> SK> that reads the same data format that James is using. You can look at
the
> SK> repository code to see how the messages are stored.
> I think that James has a pluggable repository (I saw mailbox format and
> jdbc), and I want to create another one that uses beans. James would
> just be a client to the ejb server, like it is now to a sql server.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
