- Shopping Bag ( 0 items )
Sams has assembled a team of experts in web services to provide you with a detailed reference guide on XML, SOAP, USDL and UDDI. Building Web Services with Java is in its second edition and it includes the newest standards for managing security, transactions, reliability and interoperability in web service applications. Go beyond the explanations of standards and find out how and why these tools were designed as they are and focus on practical examples of each concept. Download your source code from the ...
Ships from: Westminster, MD
Usually ships in 1-2 business days
Ships from: Avenel, NJ
Usually ships in 1-2 business days
Sams has assembled a team of experts in web services to provide you with a detailed reference guide on XML, SOAP, USDL and UDDI. Building Web Services with Java is in its second edition and it includes the newest standards for managing security, transactions, reliability and interoperability in web service applications. Go beyond the explanations of standards and find out how and why these tools were designed as they are and focus on practical examples of each concept. Download your source code from the publisher's website and work with a running example of a full enterprise solution. Learn from the best in Building Web Services with Java.
I. WEB SERVICES BASICS.
1. Web Services Overview and Service-Oriented Architectures.
What Is a Web Service?
Trends in E-Business.
Why Do We Need Web Services?
The Web Service Opportunity.
Justifying Web Services.
Web Services Interoperability Stack.
2. XML Primer.
Document- Versus Data-Centric XML.
3. The SOAP Protocol.
Simple Object Access Protocol (SOAP).
Doing Business with SkatesTown.
Inventory Check Web Service.
A Closer Look at SOAP.
The SOAP Messaging Framework.
The SOAP Body.
The SOAP Processing Model.
Versioning in SOAP.
Processing Headers and Bodies.
Faults: Error Handling in SOAP.
Objects in XML: The SOAP Data Model.
The SOAP RPC Conventions.
XML, Straight Up: Document-Style SOAP.
When to Use Which Style.
The Transport Binding Framework.
Using SOAP to Send Binary Data.
Small-Scale SOAP, Big-Time SOAP.
4. Describing Web Services.
Why Service Descriptions?
Role of Service Description in a Service-Oriented Architecture.
History of Interface Definition Languages (IDLs).
Web Services Description Language (WSDL).
A Sketch of How WSDL Maps to Java.
Nonfunctional Descriptions in WSDL.
Standardizing WSDL: W3C and WSDL 2.0.
5. Implementing Web Services with _Apache Axis.
A Brief History of Axis.
The Message APIs and SAAJ.
The Axis Client APIs.
Web Service Deployment Descriptor (WSDD).
A Guide to Web Service Styles.
From XML to Java and Back Again: The Axis Type-Mapping System.
When Things Go Wrong: Faults and Exceptions.
Axis as an Intermediary.
How to Write a Handler.
Understanding Axis Transport s.
No API Is an Island: Axis and Its Environment.
Axis Futures: A Quick Tour.
Participating in the Axis Community.
6. Discovering Web Services.
What Is Service Discovery?
UDDI (Universal Description, Discovery, _and Integration) .
Other Service Discovery Methods.
II. ENTERPRISE WEB SERVICES
7. Web Services and J2EE.
Using EJBs from Axis.
Using JSR109: Implementing _Enterprise Web Services.
8. Web Services and _Stateful Resources.
Web Services and State.
Modeling Resource Properties.
Other WS-Resource Framework Specifications.
9. Securing Web Services.
Web Services Security.
Authorization in J2EE.
J2EE and Web Services Security.
10. Web Services Reliable Messaging.
Background of the Web Services Reliable Messaging Protocol (WS-RM).
The WS-RM Specification.
WS-RM Processing Model.
SpecVersion Assertion .
Flaws and Other Thoughts on the WS-RM Spec.
Putting WS-RM into Use.
11. Web Services Transactions.
Web Services Coordination and Transaction _(WS-C/Tx).
Transactions: A Brief Introduction.
The CoordinationContext .
The CreateCoordinationContext _Operation.
The Register Operation.
WS-Coordination Fault Codes.
WS-Transaction: Atomic Transactions.
Commit and Rollback.
Two-Phase Commit Protocols.
Committing the Transaction.
Transaction Flow Overview.
Business Activity Protocol.
Reliable Delivery and Security.
12. Orchestrating Web Services.
Why Are We Composing Web Services?
Two-Level Programming Model.
Stateless and Stateful Web Services.
Evolution of Business Process Languages.
Business Process Execution Language for _Web Services.
External Interface of a Process.
Overall Structure of a Process.
Basic and Structured Activities.
Process Lifecycle and Related Activities.
Partner Links .
Properties and Correlation Sets.
Invoking Web Services and Providing Web Services.
Data Handling and Related Activities .
More Basic Activities: wait , empty .
More Structured Activities: sequence , while , switch , scope .
Fault Handling .
Compensation Handling .
Event Handling .
SkatesTown: Putting It All Together.
III. WEB SERVICES IN THE REAL WORLD
13. Web Services Interoperability.
Web Services Interoperability Organization.
WS-I Basic Profile 1.0.
Common Requirements for SOAP Envelope, WSDL Document, and XML Schema _Document.
Understanding the WSDL Document _Structure.
Importing XML Schema and WSDL _Documents.
Defining the Service Interface.
Defining a SOAP Binding.
Publishing a Service Description.
HTTP and SOAP Message Content.
Web Service Security.
WS-I Conformance Claims.
Service Provider, Requestor, and Registry Requirements.
Summary of Basic Profile 1.0 Requirements.
Future WS-I Profiles.
Basic Profile 1.1.
Simple SOAP Binding Profile 1.0.
Attachments Profile 1.0.
Basic Security Profile 1.0.
WS-I Sample Applications.
WS-I Test Tools.
Monitor Configuration File.
Message Log File.
Analyzer Configuration File.
Test Assertion Document.
Profile Configuration Report.
14. Web Services Pragmatics.
Enterprise Adoption of Web Services.
Time-Based Adoption Challenges.
Inherent Limitations of SOA.
Top-Down Versus Bottom-Up.
Policies and Processes.
Putting Web Services in Production.
Web Services Technology Map.
System Architectures for Web Services.
Features, Capabilities, and Approaches.
Tools and Platforms.
Deployment and Provisioning.
Business Process Automation Using Web _Services.
15. Epilogue: Web Services Futures.
A Roadmap for Web Services.
Age of Invention (Base SOAP, WSDL, _UDDI).
Age of Development (from Hype to _Delivery).
Age of Mainstream Acceptance (Web _Services Become Boring).
Future Trends in Web Services.
Short-Term Trends and Issues.
Appendix A:- Glossary.
Posted October 17, 2004
[A review of the SECOND EDITION, 2004.] Web Services are this potential hot new field that has been built out with a lot of proposed standards. This book goes through them, with an emphasis on implementing applications in Java. The basic idea is a set of loosely coupled programs, scattered across a computer network, which invariably is the Internet or a private Internet. Loosely coupled means asynchronous, which then favours a nonblocking message passing approach, as opposed to a blocking RPC-type setup. The messages are sent as XML. Which is independent of platform and programming language. So the book shows how to use XML in WS. But these programs on the network need to find each other. So we have UDDI being explained in the book. A large part of the book is given over to how to describe a WS. A massive standard syntax has arisen, WSDL, which is expressed in XML. Like any other book on it, this conveys the sheer verbosity of WSDL. The industry bodies that built it tried to make it expressive enough for any plausible (though yet unimplemented) usage. The problem is that WSDL is now complex and hard to learn. It is not the book itself that is bloated, but what it faithfully describes. One might wonder. Is WSDL too heavy? Could it end up like X.400 and X.500? There are indeed implementations of these, but on only a few websites.Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.
Posted October 10, 2002
Great book with a broad coverage of web services and Java. Well worth the price. However, I need a bit more depth in many areas, more than what is provided in this book. With that said, it is still a good book.Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.