| Home : Web : SOAP |
| Click "Subscribe" if you want to be notified of new or updated links in this category. | Subscribe |
|
|
SOAP Listings
|
|
Total:
83 | Displaying: 1 - 10 | Pages: 1 2 3 4 5 6 7 8 9 >> |
|
|
Sponsored Links
|
|
This is the last in a series of book excerpts from Java and SOAP on working with complex data types. In this excerpt, learn about returning custom types, using a stock market example. Returning Custom TypesIt\'s equally useful (and equally common) to return custom types from service method calls. We can enhance our trading service by offering a method that takes a single stock symbol as a parameter and returns its high and low trading prices for the day.
Updated: 05/14/2005
|
|
|
This is the third in a series of excerpts from \"Chapter 5: Working with Complex Data Types\" of Java and SOAP. This excerpt covers passing custom types as parameters. Passing Custom Types as ParametersAs Java programmers, we certainly don\'t restrict ourselves to the classes found in the standard Java packages. A substantial part of our code exists as custom types, Java classes of our own creation that embody the functionality and characteristics of the systems we\'re building.
Updated: 05/14/2005
|
|
|
This is the first in a series of excerpts from \"Chapter 5: Working with Complex Data Types\" of Java and SOAP. This excerpt covers passing arrays as parameters. In the previous chapter, we created RPC-style services in Java. Those services dealt only with simple data types. Simple data types may suffice in many situations, but you\'ll eventually need to use more complex data types, like those you\'re familiar with in your day-to-day Java programming. In this chapter we\'ll look at creating services with method parameters and return values that are arrays and Java beans.
Updated: 05/14/2005
|
|
|
This article assumes you\'re familiar with .NET Framework and C#.SUMMARYWhen creating a distributed system you frequently need to provide for communication between two entities that are not in sync. Microsoft Message Queue Server (MSMQ) provides the kind of store-and-forward messaging in a pre-built infrastructure that can help you address these kinds of messaging needs. In the past, MSMQ was accessed using a COM wrapper. Now there\'s a .NET wrapper that lets you accomplish your messaging goals easily from your Framework-based code.
Updated: 05/14/2005
|
|
|
With the introduction of Java 2 Platform, Enterprise Edition (J2EE) 1.4, Java and Web Services are fused together in a single platform. With Web Services functionality in J2EE and the Java Web Services Developer Pack (Java WSDP), developers can now take advantage of new features to build applications that feature Web Services messaging and interaction. The key to delivering this functionality is Simple Object Access Protocol (SOAP), which has become the de facto standard for this type of functionality. It is designed to provide developers with a standard for XML message formats so that they do not need to invent a custom XML message format for every service they want to make available.
Updated: 05/14/2005
|
|
|
You know the old saying, that a picture is worth a thousand words? There\'s an awful lot of binary data out there, and XML is not going to replace it all or even a significant percentage. After all, what\'s the benefit to xmlifying things like MPEG\'s or program executables?
Updated: 05/14/2005
|
|
|
Simple Object Access Protocol (SOAP) describes the packaging, encoding, and exchange of structured, typed data as an XML document. SOAP is sufficiently general yet readily extensible enough to be used for the exchange of just about any structured data. That said, SOAP is most commonly associated with Web Services, serving as the de facto standard message envelope.
Updated: 05/14/2005
|
|
|
SOAP, or the Simple Object Access Protocol, is a protocol designed to help Web applications send messages to each other. It\'s got a very simple, portable structure, based on XML, and it can travel via HTTP, so it\'s lightweight and easy to implement, plus it\'s independent of language and platform. And thus the \"Simple\" part of the acronym, without which we\'d now be learning about \"OAP,\" which isn\'t nearly as puntastic.
Updated: 05/14/2005
|
|
|
XPath is a language for addressing parts of an XML document, used most commonly by XSLT. There are various APIs for processing XPath. For the purposes of this article I will use the open source Jaxen API. Jaxen is a Java XPath engine that supports many XML parsing APIs, such as SAX, DOM4J, and DOM. It also supports namespaces, variables, and functions.
Updated: 05/14/2005
|
|
|
As you might expect from the name, XML-RPC is a way of using XML to send classic Remote Procedure Calls (RPC) over the net. XML-RPC\'s use of XML is very simple. It doesn\'t use namespaces. It doesn\'t even use attributes.Poking at the reasons behind technology standards can lead to interesting results. The really good ones, like the first ANSI C specification, include a detailed rationale for key decisions.
Updated: 05/14/2005
|
|
|
SOAP Listings
|
|
Total:
83 | Displaying: 1 - 10 | Pages: 1 2 3 4 5 6 7 8 9 >> |
|
|
