Robert Burrell Donkin wrote:
> > A generic base class for [posting to a JMS destination],
> > 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
Delegate to a message factory, and provide a <message-factory> element?
<<shrug>>
> > 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.
To post from JMS has certain requirements. We just need to satisfy them. I
would be happy if we were to annotations and container managed DI. That
would be a worthwhile project, and improvement to the Mailet API.
> efficient operation is a little more effort: session and connection
> caching would be are needed for high throughput. commons pool would be
> good enough.
Keeping in mind the fact that there is a single mailet instance, and it has
reentrancy requirements. :-)
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
