 |
 |
 |
 |
 |
 |
Tip: Implement implicit and explicit SOAP headers
You can define SOAP headers in a WSDL definition using what are commonly called explicit and implicit headers. Learn the difference between these two styles and how these differences might impact you when developing with JAX-RPC.
|
 |
Articles |
 |
15 Feb 2005 |
|
| |
Tip: Use data dictionary links for XML and Web services schemata
When designing XML and Web services schemata you will often (and ideally) reuse data elements defined in pre-existing standards. When you do, it is extremely useful to include links to such standards, providing precise data dictionary references. In so doing, you make processing and maintenance easier to automate. This tip illustrates this practice.
|
 |
Articles |
 |
20 May 2004 |
|
| |
Tip: Always use an XML declaration
The XML declaration is optional in XML files, and defaults determine most of the information in the file. However, problems are common when these defaults do not match reality -- for example, the document could use an encoding other than one of the defaults. It's always safer to make the XML declaration. In this tip, Uche Ogbuji covers what should be included in the XML declaration on all files.
|
 |
Articles |
 |
05 Jun 2007 |
|
| |
Tip: Compress XML files for efficient transmission
Binary XML has generated a lot of talk, and one of the motivators is the need for a less verbose transfer format, especially for use with Web services. One solution that is already at hand is data compression. This tip shows you how to use compression to prepare XML for transmission over Web services.
|
 |
Articles |
 |
09 Apr 2004 |
|
| |
Tip: Send and receive SOAP messages with SAAJ
In this tip, author and developer Nicholas Chase shows you how to use the SOAP with Attachments API for Java (SAAJ) to simplify the process of creating and sending SOAP messages.
|
 |
Articles |
 |
22 Jan 2008 |
|
| |
Tip: Look up XML schemata and Web services with these helpful resources
It's not always easy to find XML schemata and Web services that meet your exact needs. This tip shows you how to comb through the enormous variety of Internet resources to find schemata and Web services using common search criteria.
|
 |
Articles |
 |
11 Feb 2005 |
|
| |
Web services tip: Use asynchronous beans to improve Web services performance
Looking for ways to improve the performance of your Web services? Try
asynchronous beans. This article explains how Web services access content from a
variety of resources to perform business operations sequentially and how
asynchronous beans can enhance this.
|
 |
Articles |
 |
16 Aug 2007 |
|
| |
Autonomic computing tip: So you are building a WSDM interface
When you're building a Web Services Distributed Management (WSDM)-compliant interface for a manageable resource with Apache Muse, these four simple steps will guide you in designing the necessary Web Services Description Language (WSDL).
|
 |
Articles |
 |
20 Mar 2007 |
|
| |
Tip: Send multiple Web services requests from XForms
A typical HTML form only lets you submit to one URL at a time, which makes it difficult to retrieve information from multiple Web services. This tip shows you how to use XForms to solve that problem by using multiple submissions from a single form.
|
 |
Articles |
 |
03 Sep 2004 |
|
| |
Tip: Send part of an XForms instance to a Web service
An XForms form is handy as a Web service client because it enables you to easily send and receive an XML document, but what if you don't necessarily want to send the entire data instance? This tip explains how you can build an instance that includes a SOAP message along with other data, and then send only the SOAP message on submission.
|
 |
Articles |
 |
13 Aug 2004 |
|
| |
Autonomic computing tip: So you're building a WSDM interface
When you've built your Web Services Description Language (WSDL), this quick tip will remind you to how to map your interface to httpd-specific commands and settings using the Muse code-generation tool, WSDL2Java.
|
 |
Articles |
 |
24 Apr 2007 |
|
| |
Web services tip: Use polymorphism as an alternative to xsd:choice
xsd:choice is not always the most optimal XML schema construct. For instance, a type containing xsd:choice does not map to a user-friendly Java class using a JAX-RPC code generator. In this article, you learn about a functional equivalent to xsd:choice: polymorphism.
|
 |
Articles |
 |
20 Sep 2005 |
|
| |
Tip: SOAP 1.2 and the GET request
SOAP 1.2 brings changes that help to weave Web services more into the fabric of the Internet. One of these changes is the introduction of the GET method. GET is important because it enables various optimizations. This has been demonstrated by the Web itself, which uses GET extensively. Find out more in this tip.
|
 |
Articles |
 |
04 Mar 2004 |
|
| |
Tip: Make SOAP and Web servers cohabit peacefully
SOAP's strength is that it builds on the familiar and widely deployed Web infrastructure. That can also be a weakness because Web servers can make assumptions about Web services that are simply not true. In this installment, Benoit discusses some issues with error handling in Web services.
|
 |
Articles |
 |
19 Feb 2004 |
|
| |
Tip: Passing files to a Web service
In this tip, Benoit discusses the different solutions available for passing binary data (typically files) to a Web service.
|
 |
Articles |
 |
13 Feb 2004 |
|
| |
Tip: Use XInclude to synchronize WSDL with source schemata
In the document/literal style of Web services, the schemas of the interchange formats are often based on an existing document standard. This can cause problems synchronizing WSDL files with the standard schemata. This tip shows how to use XInclude to incorporate external schema fragments into a WSDL file.
|
 |
Articles |
 |
22 Jan 2004 |
|
| |
Tip: Use XML directly over HTTP for Web services (where appropriate)
SOAP technologies usually exchange XML over HTTP, but SOAP has its pros and cons, and a lot of discussion has focused on how to use XML more directly to communicate between applications. This tip describes the direct approach, and discusses where it is most appropriate. It also discusses how to use WSDL to describe such services.
|
 |
Articles |
 |
15 Jan 2004 |
|
| |
Tip: Send and receive SOAP messages with JAX-RPC
In this tip, IBM developer Russell Butek takes a look at JAX-RPC, a Java API that allows an application to communicate with a Web service without knowing details about the SOAP messaging protocol.
|
 |
Articles |
 |
02 Sep 2003 |
|
| |
Tip: Use XML to send SMS messages
Many developers tend to think of Web services as a way to easily move information from one place to another, but it's also important to understand how integral a Web service can be to the overall application. This tip gives some examples of using XML for Short Message Service (SMS) messages. If you're familiar with SMS, you'll find out how adding this tool to your toolbox can help you; if you're not an SMS developer, you'll see a real-life example of how Web services are integrated into an application.
|
 |
Articles |
 |
07 Jun 2004 |
|
| |
Tip: xsd:any: A cautionary tale
xsd:any is a popular feature for people designing XML schema. But it's often more trouble than it's worth. Explore some of the shortcomings of xsd:any, both in XML itself and in the JAX-RPC Java language binding, so that, even if you decide to use xsd:any, you will be more prepared to deal appropriately with it.
|
 |
Articles |
 |
13 Dec 2005 |
|
| |
Web services tip: Representations of null in XML Schema
Represent a null value in the XML-equivalent of a field when you map a null Java bean field to XML. This tip explores and compares a number of ways to do so.
|
 |
Articles |
 |
09 Aug 2005 |
|
| |
Tip: Use a proxy network library for SOAP behind a firewall
If you are trying to access a SOAP service from behind a firewall and your SOAP library does not have support for proxying network connections, you may not be able to get through by direct request. In such cases, you can use socket redirection programs to make the connection through a proxy server. Uche Ogbuji shows how to do so in this tip.
|
 |
Articles |
 |
26 Mar 2004 |
|
| |
Tip: Create an XForms form that submits a second instance
Because they can easily send and receive XML, XForms forms make great Web services clients, but using them in this way limits your control over the structure of your instance. This tip explains how to manage your data within one instance while submitting a second.
|
 |
Articles |
 |
22 Jul 2004 |
|
| |
Tip: Use XForms to send and receive Web services messages
One of the great strengths of XForms is the fact that an XForms client can send its data as XML, and that it receives XML in return. This capability can be exceptionally useful in the field of Web services, where that's exactly what gets sent and received: XML messages. In this tip, the author looks at how to use an XForms browser as a Web services client, sending a SOAP request and displaying the results directly in the browser.
|
 |
Articles |
 |
24 Jun 2004 |
|
| |
Tip: Avoid unnecessary Ajax traffic with session state
Where possible, creating Web applications -- including Ajax-based applications
-- in a RESTful way avoids a large class of bugs. However, a
pitfall of REST (Representational State Transfer) is sending duplicate data across similar
XMLHttpRequests. This tip shows how the moderate use of session
cookies can maintain just enough server-side state to
significantly reduce client-server traffic, while still allowing
fallback to cookie-free operation.
|
 |
Articles |
 |
13 Nov 2007 |
|
| |