Well, at least the JMS supports transactions and JTA is a transaction management API so maybe those are the two correct ones? I don't really see what SOAP has to do with this because SOAP itself doesn't support transactions in any way (SOAP can be used as an envelope for transaction-aware messaging -- it's just not built-in).
A.SNMP --> v1 and v2 are unsecure, security features were introduced in SNMPv3 B.SMTP --> can be secured with SSL/TLS (but then why not use HTTP instead) C.HTTPS --> this is secure and widely supported by web services products D.JTA messaging --> not a protocol but an API E.JMS messaging --> not a protocol but an API, the particular JMS vendor's proprietary communication protocol may or may not have security features (probably will, though).
However, none of these acronyms have anything to do with web service transactions. The transaction stuff happens on top of SOAP, not beneath it. I would recommend browsing your web service platform's documentation to see what kind of alternatives it provides you with. Some resources: - WS-Transaction specification - Introduction to WS-Transaction from Arjuna