A Java application wrapped as a SOAP service has the following drawbacks:

• There may be reduced performance due to the nature of converting between Java and SOAP, and back and forth.

• Since SOAP inherently has no support for transactions, this method loses atomic transactionality, that is, the ability to perform several operations in an all-or-none mode (such as debiting one bank account while crediting another, where either both transactions must be completed, or neither of them are completed).