| 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: 11 - 20 | Pages: << 1 2 3 4 5 6 7 8 9 >> |
|
|
|
With the mobile phone industry reporting better than expected sales, and news that, by the end of this year, smart phones are expected to outsell hand-held computers, it should come as no surprise that wireless application development is on the rise. Sun recently announced that by the end of 2004 there may well be more than 200,000,000 Java-enabled mobile handsets. Yet, with all the attention being paid to these microdevices (i.e., low resource mobile devices), it\'s surprising to learn that a developer wishing to build a wireless application using XML, SOAP, and web services is left behind.
Updated: 05/14/2005
|
|
|
The Electronic Business XML ( ebXML ) project released three more technical specifications for review on 28 March, including a new draft document on messaging services. This part of ebXML -- formerly known as transport, routing, and packaging -- had made more early progress than the other technical features, but it also came under more pressure to include the work of other initiatives, specifically the Simple Object Access Protocol (SOAP).Enhancements to the original SOAP specification made it easier for ebXML to join forces. But it also marked something of a change in operation for ebXML, now more willing to make accommodations with other related initiatives in order achieve its goal of a single worldwide e-business standard.
Updated: 05/14/2005
|
|
|
Like every other distributed computing architecture, Web services have also settled on a standard, well-known protocol for communication between distributed components of a system. For CORBA, the protocol was IIOP; for RMI, first it was JRMP and later it was IIOP; and in Microsoft environments it was DCOM.
Updated: 05/14/2005
|
|
|
The desire to integrate XML with pre-existing data formats has been a long-standing and persistent issue for the XML community. Users often want to leverage the structured, extensible markup conventions of XML without abandoning existing data formats that do not readily adhere to XML 1.0 syntax. Often, users want to leave their existing non-XML formats as is, to be treated as opaque sequences of octets by XML tools and infrastructure. Such an approach allows widely used formats such as JPEG and WAV to peacefully coexist with XML.
Updated: 05/14/2005
|
|
|
Over the space of a few years, the Web has completely revolutionized the way we use information technology, and as a result, our way of working has been completely transformed. The arrival of the new economy made waves which were felt all the way to the core of our information systems. Internet businesses now have to meet two escalating needs: satisfying new demands (mainly due to clients\' growing appetites), and integrating heterogeneous information systems.
Updated: 05/14/2005
|
|
|
This second article in this series dedicated to Web services comes as a sequel to the first one in which I started to tell you how you could build different kind of clients and services using MS SOAP Toolkit, Apache SOAP for Java and .NET Framework. In the last article I mentioned something about the incompatibility between a MS SOAP client and an Apache SOAP server (the infamous xsi:type). As far as I know the version 2.2 didn\'t solve this problem, which is Apache SOAP Server is still expecting all parameters to have a type specified. But, the good news is that there is a work around to this problem. Many of you sent me e-mails asking how to do this. Well it is fairly simply.
Updated: 05/14/2005
|
|
|
This article assumes you\'re familiar with C# and SOAP .SUMMARYAs more organizations adopt XML-based Web Services, the need for message-level security has become evident. WS-Security, now supported in the Microsoft .NET Framework, addresses this need. Using the WS-Security framework, developers can implement channel sinks to intercept Remoting messages as they pass through the .NET Remoting infrastructure. The sink can read the message, change it, and pass it along. During this process, the message can be signed for added security. This article explains how to implement a Remoting channel sink that will modify the Remoting message by including a UserName token in the header, then sign the body using the token.
Updated: 05/14/2005
|
|
|
This is the second part of a two-part series geared to get you quickly started with Web services and the Microsoft SOAP Toolkit. It will allow you to consume the server that we created in the first part (see http://www.15seconds.com/issue/010725.htm) of this article. Part I shows you how to use the toolkit on the server, and deploy your Web service.
Updated: 05/14/2005
|
|
|
This article will try to explain the how you can build web services and/or clients with any of the three languages: .NET, MS SOAP Toolkit and Java. But the real point of the article is to show you how you can build clients for web services from any of above-mentioned languages.
Updated: 05/14/2005
|
|
|
This article offers a basic step-by-step instruction for getting a Web service on line using the Microsoft SOAP Toolkit 2.0 Gold Release. If you do not have this version, I suggest downloading and installing it before you read any further, including the samples .First I will explain the detailed steps I took to take one of their samples and produce a Web Service ready for publishing on line. Next I will take one of their sample clients and show you how to modify it in order to work with the Web Service that we created
Updated: 05/14/2005
|
|
|
SOAP Listings
|
|
Total:
83 | Displaying: 11 - 20 | Pages: << 1 2 3 4 5 6 7 8 9 >> |
|
|
