Developing Web Services with Java APIs for XML Using WSDP

Overview

Since Web Services are interdependent, developers must be well versed in all areas to capture their true power and flexibility. Developing Web Services with Java APIs for XML (JAX Pack) offers these developers exhaustive coverage of Sun's JAX Pack, a significant product release that will enable the development of Web services using Java. Written for experienced Java developers with a solid understanding of XML, the book features five parts covering each component of JAX Pack: ...
See more details below
Available through our Marketplace sellers.
Other sellers (Paperback)
  • All (10) from $8.32   
  • New (4) from $27.39   
  • Used (6) from $8.32   
Close
Sort by
Page 1 of 1
Showing 1 – 3 of 4
Note: Marketplace items are not eligible for any BN.com coupons and promotions
$27.39
Seller since 2010

Feedback rating:

(58)

Condition:

New — never opened or used in original packaging.

Like New — packaging may have been opened. A "Like New" item is suitable to give as a gift.

Very Good — may have minor signs of wear on packaging but item works perfectly and has no damage.

Good — item is in good condition but packaging may have signs of shelf wear/aging or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Acceptable — item is in working order but may show signs of wear such as scratches or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Used — An item that has been opened and may show signs of wear. All specific defects should be noted in the Comments section associated with each item.

Refurbished — A used item that has been renewed or updated and verified to be in proper working condition. Not necessarily completed by the original manufacturer.

New
"New Original US Edition, We Ship to PO BOX Address also. EXPEDITED shipping option available for certian weight packets only."

Ships from: STERLING HEIGHTS, MI

Usually ships in 1-2 business days

  • Canadian
  • International
  • Standard, 48 States
  • Standard (AK, HI)
$29.04
Seller since 2015

Feedback rating:

(2)

Condition: New
"New, Excellent customer service. Satisfaction guaranteed!! "

Ships from: Irving, TX

Usually ships in 1-2 business days

  • Canadian
  • International
  • Standard, 48 States
  • Standard (AK, HI)
$93.54
Seller since 2015

Feedback rating:

(365)

Condition: New
Brand New Item.

Ships from: Chatham, NJ

Usually ships in 1-2 business days

  • Canadian
  • International
  • Standard, 48 States
  • Standard (AK, HI)
  • Express, 48 States
  • Express (AK, HI)
Page 1 of 1
Showing 1 – 3 of 4
Close
Sort by
Sending request ...

Overview

Since Web Services are interdependent, developers must be well versed in all areas to capture their true power and flexibility. Developing Web Services with Java APIs for XML (JAX Pack) offers these developers exhaustive coverage of Sun's JAX Pack, a significant product release that will enable the development of Web services using Java. Written for experienced Java developers with a solid understanding of XML, the book features five parts covering each component of JAX Pack: JAXP, JAXR, JAXM, JAXB, and JAX-RPC.
Read More Show Less

Editorial Reviews

From The Critics
Introduces the Java web services developer pack (WSDP) for using XML to build cross-platform web services. The authors explain how to process XML documents with SAX and DOM, transform XML with XSLT and stylesheets, use the JSP standard tag library, and write SOAP clients and servers, then address the remote procedure call protocol, interfaces to UDDI and ebXML registries, and the Java secure sockets extension. Annotation c. Book News, Inc., Portland, OR
Read More Show Less

Product Details

  • ISBN-13: 9781928994855
  • Publisher: Syngress Publishing
  • Publication date: 6/1/2002
  • Pages: 501
  • Product dimensions: 7.46 (w) x 9.16 (h) x 1.15 (d)

Table of Contents

Chapter 1 Introduction to the JWSDP

Chapter 2 Processing XML Documents with SAX

Chapter 3 Processing XML Documents with DOM

Chapter 4 XML Transformations

Chapter 5 Using JSTL (JSP Standard Tag Library)

Chapter 6 Writing SOAP Clients

Chapter 7 Writing SOAP Servers

Chapter 8 Using XML-based RPC

Chapter 9 Locating Web Services

Chapter 10 Java Secure Sockets Layer

Chapter 11 Using JWSDP Tools

Read More Show Less

First Chapter

JWSDP History

As just mentioned, the JWSDP is a collection of existing tools, and is, in some sense, a marketing response to Microsoft’s .Net initiative, gathering and highlighting existing technologies, and giving them a common name. In most cases, this works to the benefit of the user. You no longer have to worry about what APIs are going to survive in the long run; the APIs in the JWSDP have Sun’s blessing and are good choices to standardize on. You also don’t have to wonder about version compatibility between different libraries; so long as the libraries all come with the JWSDP, you shouldn’t have compatibility problems.

There are a few places where the gathering of libraries results in some oddities. In particular, the JAXM, JAXP, and JAX-RPC libraries were developed as separate initiatives by the Apache Jakarta project and the Java Community Process. Because they were developed separately, there are places where the APIs overlap—for instance, some functionalities in the JAXM is also provided in JAXP. These places are pointed out in the text. It remains unclear if future versions of the JWSDP will address these issues. The other aspect that can be confusing about the JWSDP is that some parts of it are available in different forms on the Web. For example, the JAXP libraries are shipped as a part of the JDK 1.4 release. JWSDP includes these libraries for capability with older versions of the JDK, especially as it will take some time for vendors to migrate to supporting the newer JDK releases.

Having said all that, it’s worth looking at the individual components of the JWDSP.

JAXP

The Java API for XML Processing (JAXP) provides standardized interfaces for parsing and transforming XML documents. JAXP is designed to fill a hole in the XML standard interfaces: there are standard interfaces for transforming and parsing XML, but no standard interfaces for obtaining the transformers and parsers.

When XML first started gaining popularity, there were no standards for processing it. As time went on, standards developed for processing XML, but these standards were all interface-based—they did not contain any required classes. Libraries meeting the standards did so by implementing the standard interfaces and adding their own proprietary mechanisms for creating instances of those implementing classes. So, while your XML processing code, based in the interfaces, might be portable, the small bits of code used to create those objects were not. This meant XML libraries could not be swapped in and out without making small changes to the application code. JAXP provides a standard set of interfaces, and more importantly classes, that allow for the creation of these implementation objects. JAXP does not redefine XML standards; instead, it leverages those standards (DOM, SAX, XSL) that already have wide acceptance. JAXP ensures that code utilizing the standards will not have to be changed if the XML library supporting the standard interfaces is changed.

Because JAXP does not define XML interfaces on its own, you will find that some interfaces exposed in JAXP are not in the Java or javax packages. Instead, Sun chose to adopt those standards already in wide use. This means that modifying code to use JAXP will hopefully be limited to those sections of code that create the parsers and transformers.

The next three chapters of the book cover the three aspects of JAXP: parsing using SAX and DOM parsers, and processing XML through XSL transforms.

JAXM

The Java API for XML messaging addresses a similar problem: when the SOAP (Simple Object Access Protocol) standard was proposed, it did not have a standard set of libraries for Java. Not particularly surprising, given Microsoft’s involvement in the creation of the standard, but still a problem for Java programmers. JAXM addresses this issue by providing a standard interface for SOAP 1.1 with attachments, so that Java programmers can easily send and receive SOAP messages.

JAXM provides a number of features above just the implementation of the SOAP standards. It gives vendors a mechanism for supporting reliable delivery of messages, and for partial population of SOAP messages for specific SOAP-based protocols (such as ebXML).

It was earlier mentioned that some areas of the JWSDP overlap. JAXM is one example of this. Parts of JAXM provide a simple implementation for manipulating XML documents—an example of what JAXP provides in greater detail, and with standard interfaces. Ideally, JAXM would just leverage the interfaces provided by JAXP, but it doesn’t.

This is because JAXM and JAXP were developed in parallel, by separate Java Community Process teams. It’s unfortunate and confusing, however, and makes the processing of XML documents with both JAXM and JAXP harder. If you have to receive a message via SOAP, and process it further (for example, with XSL transforms), you have to transform the document from one representation to another.

Sun has not, to my knowledge, publicly discussed this issue. However, one can hope that future JAXM releases will fix this problem.

JAXM is discussed in detail in Chapters 6 and 7 of this book.

JAX-RPC

The Java API for XML-based Remote Procedure Calls (JAX-RPC) provides a mechanism for making what appear to be object calls across a network via SOAP-based messages. JAX-RPC allows for the implementation of Web services described by WSDL (Web Service Definition Language) documents—the apparent standard for describing Web services.

With JAX-RPC, the implementation of what appears to be a Java object can, in reality, be hosted on a machine across a network (including the Internet), in any language that supports SOAP. This gives a powerful mechanism for decoupling business systems. Unlike other distributed systems (COM, CORBA), XML-based RPC can span architectures without requiring a large investment in common support software. All that is required is you process XML documents at each end. The mechanism for processing them, and the underlying system, are completely unimportant.

JAX-RPC acts much like RMI in that stub objects are created for use in invoking remote objects. Conceptually, you use the two systems identically. What differs between JAX-RPC and RMI is the format of the data transferred between the two machines. RMI uses low-level, Java-specific protocols (or CORBA IIOP), while JAX-RPC uses XML. Because of this, RMI may be faster—since the protocols are more efficient—but it is important to remember that JAX-RPC isn’t about performance, it’s about interoperability. JAX-RPC, like JAXM, was a Java Community Process project, and was developed in parallel. However, JAX-RPC does a better job of hiding the implementation details. It does not need to expose the underlying XML structures as much as JAXM did. The current reference implementation does not appear to use JAXP, but implementations from other vendors could (as could the reference implementation in future releases). Again, this is a legacy from when JAX-RPC might have been downloaded without downloading JAXP – a problem the JWSDP (and JDK 1.4) eliminates.

JAX-RPC is covered in Chapter 8 of this book.

JAXR

Once Web services have been defined via WSDL, there needs to be a mechanism for finding them. WSDL documents are often published in registries, which are public databases of WSDL documents. Registries allow users to search for services that will fulfill their needs, and download the specifications for those services.

The most common registry interfaces right now are the Universal Description Discovery and Integration (UDDI) and the ebXML (Electronic Business using XML) Registry and Repository. JAXR, the Java API for XML Registries, provides an abstract interface for querying registries; JAXR can be used to isolate the user from having to know the specifics of either UDDI or ebXML. Registries provide rich, complex mechanisms for categorizing services. A large part of the JAXR API is targeted toward providing a standardized view of these categories. This is the main reason JAXR was created as a separate library, rather than extending JNDI (Java Naming and Directory Interface, which provides a similar functionality). The categories used by JAXR would be meaningless to most JNDI users, so it did not make sense to include them in the JNDI package. On the other hand, it isn’t possible to use WSDL repositories without these categories, therefore JAXR is a package that stands on its own.

JAXR, like packages discussed previously, was developed in parallel. However, the JAXR committee did a good job of watching the other Java Community Process efforts, and has come up with a specification that can be implemented using JAX-RPC, JAXM, and JAXP.

JAXR is covered in Chapter 9 of this book.

JSSE

At this point, you might have the impression that the JWSDP is nothing but XML processing. That isn’t really true. JWSDP is closely related to the Java XML pack, which is limited to those packages discussed earlier. However, the JWSDP includes additional packages useful for creating Web-based applications.

The Java Secure Socket Extension (JSSE) is a good example of this. JSSE provides a mechanism for communicating over encrypted network connections and managing the keys associated with that encryption.

JSSE provides a royalty free implementation of SSL (Secure Sockets Layer) v3 and TLS (Transport Layer Security) 1.0 support. More importantly, the JSSE implementation may be exported from the United States, dramatically easing the adoption of secure communication in worldwide organizations. In addition to providing low-level socket support for encryption, JSSE provides additional URL handlers, so that the java.net.URL class can understand and process HTTP URLs. This means that Web services, which require transport-level security, can be easily implemented in Java. The JSSE is discussed in Chapter 10.

JSTL

Just as Web services are not only about XML, they are not only about business processing. There needs to be a mechanism for presenting functionality to end users, as well as to remote machines. It’s common to use Java Server Pages (JSPs) to encapsulate the user interface of an application; this provides a simpler interface than coding servlets by hand. However, JSPs have traditionally had to include either direct Java code or custom-written tag libraries in order to access the underlying business functionality. The JSP Standard Tag Library (JSTL) is designed to help ease this burden. JSTL provides a standard set of tags for common JSP tasks, such as iterating over a collection of objects, making database queries, and internationalizing text.

JSTL also provides for expression languages, which allow the user to directly access business objects with a simple expression. JSTL currently provides support for not one but a number of expression languages. This allows the user to choose the language that best suits their needs, but more importantly, protects the user from an upcoming JSP standard that should directly include expression languages.

JSTL comes directly from an Apache Jakarta project of the same name, which later came under the Java Community Process. JSTL is covered in Chapter 5. Ant and Tomcat.

Like JSTL, Ant comes from Apache Jakarta. Ant isn’t a Java library—rather, it’s a build tool. It’s included with the JWSDP simply because it makes writing and bundling Java applications easy to do. Ant comes with built-in tasks for creating WAR (Web Application aRchives), which are the default packing for Java Web Services. Ant is an open-source project, whose sources can be found on http://www.apache.org

Similarly, Apache Jakarta’s Tomcat is a reference implementation of the JSP and servlet standards. As such, it allows for the development hosting of servlet-based Web services, such as JAXM supports. Unlike Ant, you likely will not use Tomcat for production deployments; it does not support failover, reliable message delivery, EJBs, or a host of other production features. However, it is free, fast, and lightweight to install; you can easily run Tomcat as a test server on your development machine. Like Ant, Tomcat is open-source and available through Apache.

Along with Ant and Tomcat, JWSDP includes the WSDP (Web Services Developer Package) Registry server. This is a simple UDDI server, again for development and testing use. Unlike Ant and Tomcat, WSDP is a Sun project and is not open-source.

Ant, Tomcat, and WSDP Registry are covered in Chapter 11.

Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star

(0)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously

    If you find inappropriate content, please report it to Barnes & Noble
    Why is this product inappropriate?
    Comments (optional)