SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 65 | Next

Frank Jennings, David Salter

"Building SOA-Based Composite Applications Using NetBeans IDE 6"


protect: Boolean indicating whether existing messages are moved to a
protected area before the current message is processed hence stopping the
existing message from being overwritten.
SOAP Binding Component
The SOAP binding component (also known as the HTTP binding component)
allows JBI messages to be sent and received using SOAP over HTTP and HTTPS.
The component supports RPC Literal, RPC Encoded, and Document Literal
encoding schemes.
The component can act as a consumer providing HTTP SOAP 1.1 Services externally.
This is achieved by using the embedded Grizzly HTTP connector.
The component can also act as a provider and in this situation is capable of
invoking external web services. The WSDL Editor within NetBeans provides
support for editing the WSDL bindings and allows the address of remote SOAP
servers to be specified.
In situations where the JBI container is running inside a firewall, the SOAP binding
component can be configured to use a proxy server to enable remote web services
outside the firewall to be accessed.
Many of the properties of the SOAP binding component are global to all service
assemblies within the JBI container that make use of the binding component.
NetBeans provides support for editing these properties directly within the IDE.
???
??? ??? ???
Chapter 4
[ 65 ]
The most common properties that you will probably need to configure in your
applications are:
Default HTTP Port Number: The port number for inbound SOAP requests
when the binding component is acting as a consumer of SOAP requests.


Pages:
53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77