> JAMES is definitely the right thing, if you want to /receive/ messages > via SMTP. However, it sounds to me as if you want to /receive/ you > messages as a generically formatted XML message.
There is no reason why the message body can't be XML. > I would use SOAP for this. Are you aware that there are SOAP bindings for SMTP? ref: http://xml.apache.org/soap/faq/faq_chawke_smtp.html http://www.pocketsoap.com/specs/smtpbinding/ > Check out the Axis project, at http://xml.apache.org/axis. AXIS is an excellent package, and has an transports for HTTP, SMTP and JMS. I may be wrong, but I'm not sure if AXIS current supports server endpoints other than HTTP. One of my thoughts, which I've added to the Wiki, has been to support SOAP services in James. I imagine that this would mostly involve matchers & mailets. If you are interested in SOAP, perhaps you'd like to contribute in this area. By the way, I am interested to hear of your SOAP Service for SMS. > * An XSLT transformation will not output SMTP or SMS. I presume that he intended to use the XLST transform to produce the desired content for the desired target messaging system. --- Noel -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
