Serge Knystautas wrote: > > Guys, > > I was going to commit this, but wanted to run it by you just since it > introduces another dependency.
Ugh! Surely this is an optional feature. If people want to use it only then should they need to add the dependencies. If and when we move to OSGi, choosing to incorporate a feature will automagically ensure that the dependencies are present. Until then an optional mailet needs to be manually supplied with its dependents. > The biggest challenge I face with developing mail-apps is that it's a > pain to restart James and manage all the dependencies. Also, my > mail-apps are typically just feature extensions of a webapp. > > To address those two issues, what I want is a mailet that did an RPC > with the email and recipient address(s) and consume the email. This > takes any business logic and DAO and whatever else out of James and > lets me leave it in the webapp. > > The easiest way I know to do this is use the Hessian protocol. > (http://www.caucho.com/hessian/). It's Apache-style licensed, > implemented in numerous languages, and really is dirt simple web > services. The mailet would be as simple as configuring the URL to > call for the hessian service. The hessian service would implement a > one-line interface that accepts a MimeMessage and recipients (well, > the Mail object). There are a bunch of ways that people are already using a Mailet to distribute work remotely. Even BEA published a Dev2Dev article on how to use a Mailet to feed a JMS queue. If we could come up with a way of plugging an arbitary consumer - JMS, SOAP, Hessian, whatever - this would be core. I don't think blessing Hessian as core is a good move. It may be neat but it isn't special. Also, what is often forgotten is that SMTP is itself a distributable protocol. In many cases all that is required is a simple redirection of the mail to a private SMTP server (James instance) doing whatever it needs to do with the filtered mail it receives. > I can throw some examples together in the wiki if that would help. This would be cool. -- Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
