On 5/6/07, David Blevins <[EMAIL PROTECTED]> wrote:
On May 6, 2007, at 6:26 AM, robert burrell donkin wrote: > On 5/3/07, David Blevins <[EMAIL PROTECTED]> wrote: >> >> On May 3, 2007, at 2:55 AM, Søren Hilmer wrote: >> > On Thu, May 3, 2007 11:40, Bernd Fondermann wrote: >> >> On 5/3/07, Søren Hilmer <[EMAIL PROTECTED]> wrote: >> >>> >> >>> Also I might be wrong, but as we talk directly to the network, >> the >> >>> authorized way to integrate into an EJB container is through a >> JCA >> >>> adapter, and they are kind of beastly to implement :-) >> >> >> >> Unfortunately, you aren't wrong :-) >> > >> > No, actually I did not believe I was :-) >> >> They can definitely get a little convoluted, but you wouldn't need to >> support transacted delivery, security or outbound connections which >> does cut the problem space down considerably. It'd definitely be a >> doable task. If you were to try it I'd recommend liberally swiping >> ActiveMQ's Resoure Adapter code and just start tearing out bits and >> reworking it for James. I'm sure they have unit tests for it and >> everything. >> >> It's actually something I've hoped would happen. I know at some >> apachecon a couple years ago I cornered some poor JAMES developer and >> bored him for a good 45 minutes on the benefits of having a JAMES JCA >> adapter so people could write MDBs that consumed email. Ok... so >> maybe I did that more than once :) > > there are some interesting possibilities in this area both inbound > and outbound I never really considered outbound as javamail sessions are already a built-in supported type for javaee. What kind of neat things do you imagine?
both advanced and integrated email capabilities in java including mix'n'match busing rather than posting an email to a particular server using a particular protocol, post to a mail queue. this could be the input spool of an embedded email server, transport (either using a conventional email protocol or a mail bus) to a remote email server or just another mail to be processed by an MDB or mailet in a container (either local or remote). being protocol agnostic has a lot of advantages given the progress which has been made on buses. shouldn't matter whether the mail is transported through SMTP, IMAP, web services, JMS, HTTP or whatever. the java developer should just post'n'go. - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
