On Dec 1, 2007 6:17 PM, Noel J. Bergman <[EMAIL PROTECTED]> wrote: > 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.
i'd prefer delegation to inheritance > An effort of a few moments to code it, leaving configuring JNDI is an > exercise for the reader. probably better to use a generic messaging interface and push JNDI or local brokering behind it. same interface can then be used for any MOM. efficient operation is a little more effort: session and connection caching would be are needed for high throughput. commons pool would be good enough. but all in all a nice little project - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
