Skip Navigation Links | |
Exit Print View | |
Oracle Java CAPS HTTP Binding Component User's Guide Java CAPS Documentation |
Using the HTTP Binding Component
About the HTTP Binding Component
HTTP/SOAP Binding Architecture
HTTP Binding Component Features
HTTP Binding Component Example Scenario
SOAP 1.1 WSDL Extensibility Elements
SOAP 1.1 header and headerfault Elements
SOAP 1.2 WSDL Extensibility Elements
SOAP 1.2 header and headerfault Elements
HTTP WSDL Extensibility Elements
Configuring the HTTP Binding Component for HTTP Get Interactions
Using the HTTP Binding Component with the HTTP POST Method
Configuring the HTTP Binding Component for HTTP Get Interactions
HTTP POST Treatment of http:urlEncoded and http:urlReplacement
HTTP Binding Component Runtime Properties
HTTP Binding Component Client Endpoint Properties
Accessing the HTTP Binding Component Client Endpoint Properties
HTTP BC Client Endpoint Configuration Properties
Using Normalized Message Properties to Propagate Binding Context Information
Using Normalized Message Properties in a BPEL Process
Using Predefined Normalized Message Properties in a BPEL Process
To use predefined normalized message properties in a BPEL process
Adding Additional Normalized Message Properties to a BPEL Process
To add a Normalized Message Property Shortcut to a BPEL process
To edit an NM Property Shortcut
To delete an NM Property Shortcut
To add a Normalized Message Property to a BPEL process
BPEL Code Generation Using NM Properties
SOAP HTTP Binding Component Specific Normalized Message Properties
Quality of Service (QOS) Features
Configuring the Quality of Service Properties
Message Throttling: Configuring and Using
Configuring the HTTP Binding Component Endpoint for Throttling
Redelivery: Configuring and Using
Using the Tango Web Service Features with the HTTP Binding Component
Configuring Reliable Message Delivery
Installing the Synchronous BPEL Process sample
Configuring Web Services for a Project from the CASA Editor
Configuring the Tango Web Services Attributes exposed by the HTTP Binding Component
Accessing the Tango (WSIT) Web Service Attribute Configuration
Accessing the WS-Policy Attachment Editor for a Specific Endpoint
Server Configuration--Web Service Attributes
Client Configuration -- Web Service Attributes
HTTP Binding Component Security
Using Basic Authentication with the HTTP Binding Component
Basic Authentication Supported Features
Authentication Mechanisms for Consumer Endpoints
WssTokenCompare Username/Password Authentication
Using the Access Manager for Authentication and Authorization
Installing the Access Manager Add-on
Installing Access Manager with Java Application Platform SDK
Configure the HTTP Binding Component to use Access Manager
Using the OpenSSO Web Services Security (WSS) Agent for Authentication and Authorization
Install OpenSSO Enterprise Server
Configure the HTTP Binding Component to use OpenSSO Web Service Security
Using the GlassFish Realm Security to Authenticate the HTTP Client Credentials
Configuring Security Mechanisms
Username Authentication with Symmetric Key
Message Authentication over SSL
SAML Sender Vouches with Certificates
STS Issued Token with Service Certificate
Using Application Variables to Define Name/Value Pairs
Using Application Variables for password protection
Creating a password Application Variable
Using Application Configuration to Configure Connectivity Parameters
To apply a named Config Extension to the Application Configuration
Clustering Support for the HTTP Binding Component
Configuring the HTTP Binding Component for Clustering
Understanding the ${HttpDefaultPort} Token
Validating HTTP Extensibility Elements from the WSDL Editor
Adding a SOAP Template to a WSDL Document
Adding an HTTP Template to a WSDL Document
Web Service Client Calling an Operation Using HTTP Basic Authentication
Web Service Implementing an Operation Protected by HTTP Basic Authentication
Web Service Client Calling an Operation Using SSL Authentication
Web Service Implements an Operation Protected by SSL Authentication
The HTTP BC implements the HTTP 1.1 POST binding defined in the WSDL 1.1 specification, enabling applications to consume or provide services from the JBI environment using a web browser-like HTTP GET interaction.
To configure the HTTP Binding Component to function for HTTP POST interactions, the WSDL file of the service to which the binding component is acting as proxy, needs to use the following HTTP binding language elements defined in the WSDL 1.1 Specification:
An <http:binding> element indicating that a WSDL binding uses HTTP POST.
An <http:address> element representing the address of the port.
An <http:operation> element representing a relative address for each operation, that is relative to the <http:address> defined by the port.
An <http:urlEncoded> and <http:urlReplacement> element to indicate how all of the message parts of a request are encoded and made a part of the HTTP request URI.
Examples that demonstrate how to configure the HTTP Binding Component as a provider proxy or consumer proxy are available at Using the HTTP Binding Component with the HTTP GET method and Using the HTTP Binding Component with the HTTP POST method.
Note - Currently the HTTP Binding Component only supports the use of <http:urlReplacement> and <http:urlEncoded> with HTTP GET.
For information on the Binding details for these elements, see Binding Details.
The HTTP Binding Component does not use the WSDL HTTP Binding consistently across GET and POST-style interactions, due to request structure differences between GET and POST requests.
The differences are:
GET requests do not carry additional data aside from what is included in the URL (and in the HTTP headers).
POST requests can send additional data in the request entity body. For example, when a web browser is used to submit a form (or upload a file through a form) by POST, the form data, or the contents of the file, is sent as the body of the request. The data is not made part of the request URL.
Because of these differences, the current HTTP Binding Component implementation considers http:urlEncoded and http:urlReplacement to be meaningful only when used in conjunction with HTTP GET, because these binding elements refer to URL encoding styles that apply only to GET requests.
For HTTP POST, the current implementation ignores both http:urlEncoded and http:urlReplacement binding elements.