Re: Notification server

[Aaron Knauf]

Noel J. Bergman wrote:

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.

Absolutely correct. SOAP is a fully featured specification for sending more than just your basic XML message via a number of transports. Whether or not the transport is SMTP, SOAP is a great way of doing this kind of thing.

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/

Yup, I certainly am.

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.

I haven't been keeping up with the Axis dev list recently, so I am not sure, either.

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.

I have thought about this one, too. The approach that I would investigate first would be to embed Axis within a Mailet. I don't know how much I want to bite off here. If the config stuff flies, I'll see how that one goes first. (Incidentally, Mailet configuration would have to be beefed up to support SOAP.)

By the way, I am interested to hear of your SOAP Service for SMS.

The SOAP part of this is quite simple. All of our applications that send SMS messages (and there are alot) use an stateless session EJB to submit a ShortMessage object to an application that we wrote to take care of the SMPP communications and the high load handling involved. We simply use apache soap (not axis) to map a SOAP message to a ShortMessage object a make the EJB call.

The main reason that we use SOAP at all is because of incompatibilities between different versions of Weblogic.

In the next version of our SMS handling application, we may make SOAP the primary interface, rather than EJB. (Much more open.)


Cheers

ADK


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>