File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Web Services and the fly likes protocol to use with SOAP message Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "protocol to use with SOAP message" Watch "protocol to use with SOAP message" New topic
Author

protocol to use with SOAP message

faiza athar
Ranch Hand

Joined: Oct 30, 2001
Posts: 136
which protocol supports tranactions when using SOAP messages.
A.SNMP
B.SMTP
C.HTTPS
D.JTA messaging
E.JMS messaging
Pls correct me, is it c and e??
i'm confused if jta is used with soap?
Lasse Koskela
author
Sheriff

Joined: Jan 23, 2002
Posts: 11962
    
    5
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).


Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
faiza athar
Ranch Hand

Joined: Oct 30, 2001
Posts: 136
e.g for a credit processing system in a bank, i choose to do web service with soap messages, then which protocol will support txs and will be secure.
so the ans would be jms, https.
???
Lasse Koskela
author
Sheriff

Joined: Jan 23, 2002
Posts: 11962
    
    5
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
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: protocol to use with SOAP message