Robert Burrell Donkin wrote:
> Tom Brown wrote:
> > 3. As SMTP-to-JMS bridge (reverse of #1)
> > a. JAMES receives mail
> > b. JAMES publishes mail to specific JMS queue or topic
> > c. mail is processed/stored/whatever by any interested listeners
> fancy volunteering to contribute some code to do this?
The only relevant bit is 3.b, which is a mailet. The mailet would take the
message, formulate some ad-hoc JMS message as desired, and post it to a
destination:
<destination>...</destination>
<destination-type>[queue|topic]</destination-type>
<connection-factory>...</connection-factory>
<other elements as desired>
A generic base class for this, with an abstract createMessage method, would
let people create their own subclass to provide whatever ad-hoc JMS message
they desire.
An effort of a few moments to code it, leaving configuring JNDI is an
exercise for the reader.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
