Why don't we simply put the mailet in the Jar and import the package in
config.xml ?
A mailet already is a class that handle a mail and could be able to send
the message to remote service.
Maybe we should support fully qualified class names in the class
attribute for our mailets in config.xml: it seems cleaner than importing
full packages at the start of the config.xml and would allow the use of
multiple mailets with the same name but in different packages.
Stefano
Bernd Fondermann wrote:
interesting aspect to have a RPC-mailet. maybe this could be done with a
more generic approach: a mailet which takes as configuration parameters
a. a jar (hessian.jar, activemq.jar, whatever is neccessary) which it
loads on its own
and
b. a class contained within the jar which is instantiated by the mailet
this class has all the logic to send the mail from the mailet to the
remote service.
plusses:
there would be no explicit dependency on build time.
it would be open to any service.
...but maybe this is just over-engeneering ;-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
