Using the HTTP Binding Component

Contents

• Using the HTTP Binding Component
• About the HTTP Binding Component
• HTTP/SOAP Binding Architecture
• HTTP Binding Component Features
  • HTTP/SOAP Binding Component Features
  • Service Provider Features
  • Service Consumer Features
  • Security Features
• HTTP Binding Component Example Scenario
• SOAP Processing
• HTTP Processing
• HTTP GET and POST Processing
• HTTP Binding Component Runtime Properties
• HTTP Binding Component Client Endpoint Properties
• Using Normalized Message Properties to Propagate Binding Context Information
• Configuring Quality of Service (QOS) Features
• Using the Tango Web Service Attributes with the HTTP Binding Component
• Configuring Web Service Attributes
• HTTP Binding Component Security
• Using Application Variables to Define Name/Value Pairs
• Using Application Configuration to Configure Connectivity Parameters
• Logging and Statistics Monitoring
• Using WS-Atomic Transaction
• Clustering Support for the HTTP Binding Component
• Common User Scenarios

HTTP Binding Component Features

Features of the HTTP/SOAP Binding Component include the following:

• Supports the WSDL 1.1, SOAP 1.1, SOAP 1.2 specifications and Basic Profile 1.1. Message exchanges to and from this binding component make use of the JBI WSDL 1.1 wrapper for the normalized message
  
• Implements HTTP and SOAP binding as defined by the WSDL 1.1 specification
  
• Follows WS-I 1.0 conventions and adds additional support for non-conforming components
  
• Supports Document and Remote Procedure Call (RPC) style web services
  
• Supports literal and encoded use
  
• Supports the common convention of WSDL retrieval, such as <service uri>?wsdl
  
• Uses XML Catalogs following the OASIS Committee Specification, which enable the component to resolve schemas locally without resorting to network access
  
• Supports JBI service unit deployments to define the web services to provide or consume
  
• Makes use of the WSDL extensibility (standard HTTP and SOAP extensions) to define external communication details for the web services to provision or consume
  
• Supports http://enterprise.netbeans.org/soa/compapp/casa/tutorials/bcbc/index.html, which allows direct HTTP Binding Component to HTTP Binding Component connections within a composite application
  
• Provides enhanced Application Variable Support
  
• Supports HTTP and HTTPS connections
  
• Provides Metro (JAX-WS, Tango/WSIT) integration to support WS-* features (such as WS-Security, WS-Addressing, WS-Reliable Messaging, WS-Transaction, and so forth) for incoming and outgoing requests
  
• Provides full JAX-WS integration for incoming and outgoing requests
  
• Supports GlassFish V2 cluster mode
  

Service Provider Features

An HTTP Binding Component acting as a service provider supports sending HTTP or SOAP messages to an external web service.

Service provider features include:

• Outbound requests handled through the Java API for XML Web Services (JAX-WS)
  
• Support for proxy and proxy server authentication
  

Service Consumer Features

The HTTP Binding Component, acting as a service consumer, services HTTP requests or SOAP requests from HTTP clients, transforms (normalizes) them, and sends them to the normalized message router.

Service consumer features include:

• Uses asynchronous I/O (NIO) in the server to service thousands of concurrent incoming requests
  
• Packaged with an embedded HTTP server (Grizzly)
  
• Supports clustering

Security Features

Security features include support for transport level security through:

• Basic authentication
  
• SSL support
  

Previous
Next

This page (revision-15) was last changed on 08-May-09 15:28 PM, -0700 by rjacobus.
This page was created on 05-Nov-07 09:59 AM, -0800 by rjacobus.

Back to HTTP Binding Component Features