Why is it easy to transport SOAP messages in so many underlying protocols (HTTP, FTP, SMTP, Jabber, etc.)?
• Because it is just XML. • Because it divides messages into header and body. • Because it follows a hierarchical encoding method. • Because it is a binary encoding. • It is not. SOAP only works over HTTP. • In Axis, when you change the scope of a web service, you are changing • when the remote object is to be created and destroyed. • the namespace used by the SOAP client. • the namespace used by the SOAP server. • the availability of the object server under various conditions. • the class that the web service extends. • Say you want to deploy some of the methods in class FinanceServices as web services, what would you need to do differently if you were using Axis versus MS VS .NET? • In .NET you comment each method that should be exported while in Axis all methods in the class are exported. • In .NET you just need to click on the compile button while in Axis you need to run the java2ws program. • In .NET you just need to click on the compile button, same as in Axis. • In .NET you need
Related Questions
- There are HTTP Slow Response, FTP Slow Response, SMTP Slow Response and POP3 Slow Response in the diagnoses events when I run Colasoft Capsa. Whats wrong and does it severe?
- Why is it easy to transport SOAP messages in so many underlying protocols (HTTP, FTP, SMTP, Jabber, etc.)?
- How does XAML relate to XML-based web service transport protocols (XP, SOAP, ebXML Transport)?
