List of Examples

• 1-1 WSDL Fragment with an Improperly Named Input Parameter
• 1-2 XML Schema Fragment for a .NET Web Service
• 1-3 SOAP Message Generated from a .NET DataSet Data Type
• 1-4 SOAP Request Fragment, Illustrating Value of SOAPAction
• 1-5 Incorrect Response Returned by .NET
• 1-6 Setting the Routing Style of a Service on the .NET Platform
• 1-7 WSDL Fragment, Where the Source Element is Not Nillable
• 1-8 Request Message, With xsi:nil Set to true
• 1-9 Sample SOAP Fault Response from OracleAS Web Services
• 1-10 Request Message, Omitting Optional Elements
• 1-11 Sample SOAP Message
• 1-12 WSDL Fragment, with Mappings for Input and Output Parameters
• 1-13 Client Application Fragment that Passes a Large long Value
• 1-14 Sample SOAP Fault Sent by the .NET Platform
• 1-15 Java Code Fragment to Access a .NET Web Service
• 1-16 SOAP Response Message from a .NET Web Service that Returns a Date
• 1-17 Printout of a Java Calendar Object
• 2-1 swaRef Attachment Referenced in the soapbind:body Element
• 2-2 WSDL that References a swaRef Attachment
• 2-3 Sample Generated Service Endpoint Interface with an Attachment
• 2-4 Implementation of a Service Endpoint Interface
• 2-5 Creating a New Instance of AttachmentPart
• 2-6 Service Endpoint Interface with a Method that Passes Attachments
• 2-7 WSDL Fragment, Displaying only Type Definitions
• 2-8 SWA Attachment Referenced in the mime:content Element
• 2-9 WSDL that References a SWA Attachment
• 2-10 Generated Interface with a SWA Attachment
• 2-11 WSDL Fragment, that Defines a SOAP Fault
• 2-12 WSDL Fragment, Displaying only Port Types and Binding Declarations
• 2-13 Implementing a Method that Throws Faults with Attachments
• 2-14 Web Service Client with Code for Retrieving Attachments
• 2-15 Sample Message with a Streamed Attachment
• 2-16 Service that Uses Streaming Attachments
• 2-17 Service Implementation that Employs Streaming Attachments
• 2-18 WSDL Elements for a Streaming Attachment
• 2-19 Client Code to Store a Streaming Attachment
• 2-20 XML Schema for Streaming Attachments
• 2-21 WSDL Skeleton, with the Extensions for DIME Encoding
• 3-1 Properties and Management Configuration Dynamically Passed to a DII Client
• 3-2 Management Configuration Dynamically Passed to a Dynamic Proxy
• 3-3 Properties and Management Configuration Dynamically Passed to a Static Proxy
• 3-4 Management Configuration Dynamically Passed to a J2EE Web Service Client
• 3-5 web.xml—Static Configuration for a Servlet or JSP Web Service Client
• 3-6 orion-web.xml—Static Configuration and Management Information for a Servlet or JSP Web Service Client
• 3-7 ejb-jar.xml—Static Configuration for an EJB Web Service Client
• 3-8 orion-ejb-jar.xml—Static Configuration and Management Information for an EJB Web Service Client
• 3-9 application-client.xml—Static Configuration for an Application Client Web Service Client
• 3-10 orion-application-client.xml—Static Configuration and Management Information for an Application Client Web Service Client
• 5-1 reliability-tables.sql with Modified Column Widths
• 5-2 Port-Level Reliability Set for an In-Memory Store
• 5-3 Port Level Reliability Set for a Configured Datasource on the Server
• 5-4 Operation-Level Reliability Elements in the Server-Side Configuration File
• 5-5 WSDL Fragment, Containing Capability Assertions for Reliability
• 5-6 Port-Level Reliability Elements in the Client-Side Configuration File
• 5-7 Operation-Level Reliability Elements in the Client-Side Configuration File
• 5-8 Database Connection for a J2SE Client
• 5-9 Database Connection for a J2EE Client
• 5-10 Listener Configuration for a J2EE Client
• 5-11 Reliability Code for a Static Stub Client
• 5-12 Reliability Code for a DII Client
• 5-13 Message Ordering on the Client
• 5-14 Passing a Reliability Configuration in a Bottom Up Web Service Assembly
• 5-15 Sample Server-Side Reliability Configuration
• 5-16 Passing a Reliability Configuration in a Top Down Web Service Assembly
• 5-17 Passing a Reliability Configuration in a Web Service Client Assembly
• 5-18 Sample Client-Side Reliability Configuration
• 6-1 Sample SOAP Message in the Audit Log
• 6-2 Operation-Level Auditing Element in the Server-Side Configuration File
• 6-3 Sample Client-Side orion-web.xml with an Auditing Configuration
• 6-4 Sample Log File Entry
• 6-5 Port-Level Logging Elements in the Server-Side Configuration File
• 6-6 Operation-Level Logging Elements in the Server-Side Configuration File
• 6-7 Passing an Auditing and Logging Configuration in a Bottom Up Web Service Assembly
• 6-8 Sample Server-Side Auditing and Logging Configuration
• 6-9 Passing an Auditing and Logging Configuration in a Top Down Web Service Assembly
• 6-10 Passing an Auditing Configuration in a Web Service Client Assembly
• 6-11 Sample Client-Side Auditing Configuration
• 6-12 orion-web.xml File Edited to Contain an Auditing Configuration
• 7-1 Sample Custom Java Type Value Class
• 7-2 Sample SOAPElementSerializer Implementation
• 7-3 Sample Java Service Endpoint Interface
• 7-4 Sample Implementation of a Java Service Endpoint Interface
• 7-5 Sample User-Defined Bean Type
• 7-6 Sample oracle-webservices Type Mapping Configuration
• 7-7 Client-Side Proxy Code, Using Custom Java Type Values
• 7-8 Sample Schema Document
• 7-9 Implementation of the Custom Java Type InitItem
• 7-10 Custom Serializer Implementation to Map MyInitItem to InitItem
• 7-11 Custom Serializer Implementation to Map java.lang.String to xsd:string
• 7-12 Schema Definitions of InitItem and StringItem
• 7-13 Definition of the Items Class
• 7-14 Service Endpoint Interface for MyEndpointIntf
• 7-15 Service Endpoint Implementation
• 7-16 Custom Type Mapping File, with Pre-Generated Value Type Classes
• 7-17 Custom Type Mapping File, with Edited Value Type Classes
• 7-18 Client Program Using Default Generated Value Types
• 7-19 Client Side Custom Type Mapping File
• 7-20 Client Code Incorporating Custom Type Mapping and Custom Serializer
• 8-1 XML Code to Identify Sender Queue and Receiver Queue
• 8-2 WSDL with a JMS Transport Configuration
• 8-3 oracle-webservices.xml with JMS Transport Configuration
• 8-4 Client Stub Code to Send Messages with JMS Transport
• 8-5 Setting replyTo* Parameters Programmatically
• 8-6 DII Client Code to Send Messages Through JMS Transport
• 9-1 Command Line, Using wsifJavaBinding to Configure a Single Java Port
• 9-2 Ant Task, Using wsifJavaBinding to Configure a Single Java Port
• 9-3 Using wsifJavaPort to Configure a Single Java Port
• 9-4 WSDL Extensions for WSIF Java Bindings
• 9-5 Using wsifJavaPort to Configure a WSIF Java Port and a SOAP Java Port
• 9-6 Schema Definitions to Support WSIF Java Bindings
• 9-7 Command Line, Using wsifEjbBinding to Configure a Single EJB Port
• 9-8 Ant Task, Using wsifEjbBinding to Configure a Single EJB Port
• 9-9 Using wsifEjbPort to Configure a Single EJB Port
• 9-10 WSDL Extensions for WSIF EJB Bindings
• 9-11 Using wsifEjbPort to Configure Multiple EJB Ports
• 9-12 Schema Definitions to Support WSIF EJB Bindings
• 9-13 Command Line, Using wsifDbBinding to Configure a Single Database Resource Port
• 9-14 Ant Task, Using wsifDbBinding to Configure a Single Database Resource Port
• 9-15 WSDL Extensions for WSIF Database Resource Bindings
• 9-16 Ant Task, Using wsifDbPort to Configure a Single Database Resource Port
• 9-17 WSDL Extensions for WSIF Database Resource Bindings
• 9-18 Ant Task, Using wsifDbPort to Configure Multiple Database Resource Ports
• 9-19 Schema Definitions to Support WSIF Database Resource Bindings
• 9-20 Sample WSIF Client Code
• 9-21 Using a WSIF Client as a Dynamic Proxy
• 9-22 Client Code to Pass a User Name and Password to the Service
• 9-23 WSIF Client Configuration File
• 9-24 Adding an Attachment to a Message with the WSIF API
• 9-25 Adding an Attachment to a Message with the WSIF API
• 10-1 Definition of Provider-Policy-Type
• 10-2 XML Structure of Policy Element
• 10-3 web.xml Fragment, with ProviderServlet and the URL to Which it Listens
• 10-4 Extension of a ProviderServlet Method with a Call to super
• 10-5 oracle-webservices.xml Fragment, with a <provider-description> Clause
• 10-6 Provider Elements in the web.xml Deployment Descriptor
• 10-7 Dynamically Registering a Provider-Managed Endpoint
• 10-8 Package Structure for a Web Service with a Provider Application
• A-1 Global Elements of the wsmgmt.xml File
• A-2 Port Level Elements in the wsmgmt.xml File
• A-3 Sample wsmgmt.xml File
• B-1 Package to Namespace Mapping Elements in the JAX-RPC Mapping File
• B-2 Mapping File that Specifies a Single Package for Multiple Namespaces
• D-1 WSDL Definition of an Array of Strings for the RPC-Encoded Format
• D-2 WSDL Definition of a Multi-Dimensional Array of an Array of Strings
• E-1 Basic Call with parameter registration and Java bindings
• E-2 Configured Call with Java bindings, but without parameter registration
• E-3 Configured Call with registration of wrapper parameters and Java bindings
• E-4 Basic Call with SOAPElement, but without parameter registration
• E-5 Configured Call with a WSDL, complex return parameter registration, and Java bindings
• E-6 Basic Call with document-literal invocation and SOAPElement, but without parameter registration
• E-7 Configured Call with RPC-encoded invocation, complex parameter registration, and Java bindings