This chapter describes how to configure Web Service bindings for SCA services and SCA references.
This chapter includes the following sections:
Configure Web Service bindings in the <binding.ws> element in the Spring application context file for your application. For background information, see the following:
For general information about configuring the Spring application context for a WebLogic Spring SCA application, see Chapter 6, "Configuring the Spring Application Context."
For the schema that defines the <binding.ws> element, see Appendix A, "WebLogic SCA Binding Schema (weblogic-sca-binding.xsd)."
The Web Service binding can be applied to SCA services and SCA references. It does the following:
Parses the <binding.ws> element and, for service bindings, generates a WSDL of the service to be published.
For service bindings, publishes the "Plain Old Java Object" (POJO) as a Java API for XML-Based Web Services (JAX-WS) Web Service.
Accepts requests for the published services and performs reference invocations to the Web Services.
An example of a Web Service binding on a service is shown in Example 8-1:
Example 8-1 Web Service Binding on a Service
<sca:service name="SCAService"
type="com.oracle.test.SayHello"
target="hello">
<wlsb:binding.ws"
name="mysvcname"
port="myportname"
uri="/mysvcnameuri"/>
</sca:service>
An example of a Web Service binding on a reference is shown in Example 8-2:
Example 8-2 Web Service Binding on a Reference
<sca:reference name="SCAReference" type="com.oracle.test.SayHelloRef">
<wlsb:binding.ws"
location="http://localhost:7001/wlscaapp/myrefsvcnameuri"
port="http://test.oracle.com#wsdl.endpoint(SCAService2/myrefportname)"/>
</sca:reference>
For reference bindings referring to services outside the current application, it is expected that the contract class used for the reference is generated from the WSDL using client tools such as the WebLogic clientgen Ant task or Oracle JDeveloper.
Caution:
If the contract class is not generated from JAX-WS compatible client tools, certain types of functionality may not work correctly.
The type specified in the type attribute of sca:reference must be a JAX-WS compatible interface, generated from the external WSDL using a JAX-WS compatible client generation tool such as the JAX-WS wsimport tool, the WebLogic clientgen Ant task, Oracle JDeveloper, or Oracle Enterprise Pack for Eclipse (OEPE).
Attributes of the <binding.ws> element are as follows:
Optional. Specifies the type of databinding to use for converting SOAP messages to and from Java. Valid values are:
toplink.jaxb (default)
Specifies that the databinding use TopLink/EclipseLink JAXB (JAXB2) from EclipseLink 2.0. For information on those technologies, see Oracle® Fusion Middleware Developer's Guide for Oracle TopLink and EclipseLink at http://www.eclipse.org/eclipselink/.
toplink.sdo - Toplink/EclipseLink SDO from EclipseLink 2.0
Specifies that the databinding use Toplink/EclipseLink Service Data Objects (SDO) from EclipseLink 2.0. See EclipseLink at http://www.eclipse.org/eclipselink/.
Depending on the type of databinding, you may also have to use the <property> subelement of binding.ws. See:
glassfish.jaxb
Specifies that the databinding use the Java Architecture for XML Binding 2.x (JAXB2) Reference Implementation (JAXB RI). For information about the JAXB RI, see Glassfish > Metro > JAXB at https://jaxb.dev.java.net/.
Required for sca:reference bindings only. Specifies the location (that is, URL) where the external reference can be found. The WSDL must be made available by appending ?wsdl to this location.
Optional. Specifies the name of the binding.
For sca:service bindings, this name is published as the service name in the WSDL. It overrides the name specified in name attribute of the sca:service element.
Optional for sca:service bindings. Specifies the port name to use for the service endpoint.
Required for sca:reference bindings. Specifies the WSDL port that this reference points to in the external Web Service.
This should be of the form namespace uri#wsdl.endpoint(servicename/portname).
Optional. Specifies the SOAP version of the Web Service. Valid values are 1.1 and 1.2. Defaults to 1.1.
Required for sca:service bindings only. Specifies the location, relative to the context-root of the SCA application, where the Web Service must be published for this SCA service.
The <binding.ws> element can have the following subelements:
The <PolicyReference> subelement of <binding.ws> specifies a reference to the security policy to use. It has the following attributes:
Specifies the location of the policy. Only built-in WebLogic Server security policies are supported in this release.
Optional. Specifies whether the policy is inbound, outbound, or both. The default is both.
For more information about using the PolicyReference element to configure security policies, see Configuring Security..
The <property> subelement of <binding.ws> has a name attribute that accepts the following property names:
weblogic.sca.binding.ws.sdoSchemaFile
Specifies the location of the schema file for SDO bindings. See Configuring TopLink/EclipseLink SDO Databinding.
weblogic.sca.binding.ws.externalCustomizationFile
Specifies an external databinding customizing XML file. See Configuring Custom Databinding.
weblogic.sca.binding.ws.referenceWsdlCacheTimeoutMins
Configures WSDL caching when invoking references. To enable caching and to specify the caching timeout period, specify a positive number to indicate the number of minutes. To disable WSDL caching, specify zero or a negative value. If this property is not set, caching is enabled with a default timeout of 60 (minutes).
Use the <PolicyReference> element to configure security policies for Web Services bindings. See also PolicyReference Element.
The following security mechanisms are supported:
Username token with message protection (WS-Security 1.1)
X509 certificate authentication with message protection (WS-Security 1.1)
Anonymous with message protection (WS-Security 1.1)
ID Propagation using SAML token (sender-vouches) with message protection (WS-Security 1.1)
Username token over SSL
SAML token (Sender Vouches) over SSL
An example of a security configuration for an SCA service is shown in Example 8-3
Example 8-3 Security Configuration Example
<sca:service
name="SCAServicePolicy"
type="com.oracle.test.SayHelloRefImpl"
target="hello2">
<binding.ws
xmlns="http://xmlns.oracle.com/weblogic/weblogic-sca-binding"
name="mypolicysvcname"
port="uri:myns#wsdl.endpoint(mypolicysvc/mypolicyport)"
uri="/mypolicyuri">
<PolicyReference
xmlns="http://schemas.xmlsoap.org/ws/2004/09/policy"
uri="policy:Wssp1.2-Https-UsernameToken-Plain.xml"
direction="inbound" />
</binding.ws>
</sca:service>
To specify that an SCA service or reference will use an Oracle Web Services Manager (OWSM) security policy, instead of a WebLogic security policy, set the optional weblogic.sca.binding.ws.usingOwsmPolicies property to true. Example 8-4 and Example 8-5 show OWSM policies specified for an SCA service and an SCA reference, respectively.
Example 8-4 Security Configuration for SCA Service Using an OWSM Policy
<sca:service name="SCAServicePolicy"
type="com.oracle.test.SayHelloRefImpl"
target="hello2">
<binding.ws xmlns="http://xmlns.oracle.com/weblogic/weblogic-sca-binding"
name="mypolicysvcname"
port="uri:myns#wsdl.endpoint(mypolicysvc/mypolicyport)"
uri="/mypolicyuri">
<PolicyReference xmlns="http://schemas.xmlsoap.org/ws/2004/09/policy"
uri="policy:oracle/wss_username_token_service_policy" />
<property name="weblogic.sca.binding.ws.usingOwsmPolicies">true</property>
</binding.ws>
</sca:service>
Example 8-5 Security Configuration for SCA Reference Using an OWSM Policy
<sca:reference name="SCAReferenceOwsmUNTPolicy"
type="com.oracle.test.SimpleSayHello">
<binding.ws xmlns="http://xmlns.oracle.com/weblogic/weblogic-sca-binding"
location="http://adc2101232:7001/jscaowsm/myowsmuriunt12"
port="http://test.oracle.com#wsdl.endpoint(myowsmsvcname/myowsmport)"
soapVersion="1.2">
<PolicyReference xmlns="http://schemas.xmlsoap.org/ws/2004/09/policy"
uri="policy:oracle/wss_username_token_client_policy" />
<property name="weblogic.sca.binding.ws.usingOwsmPolicies">true</property>
</binding.ws>
</sca:reference>
For more information about OWSM policies, see "Using Oracle Web Services Manager Security Policies" in Securing WebLogic Web Services for Oracle WebLogic Server.
Specify databinding as follows:
Specify the databinding type to use in the databinding attribute of <binding.ws>.
For SDO and customization files, specify additional details in the <property> subelement of <binding.ws>.
For information about configuring different kinds of databinding, see:
If a databinding type is not specified, toplink.jaxb is used.
To configure TopLink/EclipseLink JAXB databinding enter toplink.jaxb as the value for the databinding attribute in the binding.ws element.
Note:
This is the default databinding type. If nothing is specified for the databinding attribute, toplink.jaxb is used.
An example of TopLink/EclipseLink JAXB databinding is shown in Example 8-7
To configure databinding TopLink/EclipseLink SDO:
In the <binding.ws> element, enter toplink.sdo as the value for the databinding attribute.
In the <property> subelement of <binding.ws>:
Enter weblogic.sca.binding.ws.sdoSchemaFile as the value for the name attribute.
Enter the location of the schema file for the SDO bindings as the content of the element. The path must be relative to the application root, and the schema file must be bundled with the application.
An example of TopLink/EclipseLink SDO databinding is shown in Example 8-7
Example 8-7 TopLink/EclipseLink SDO Databinding
<sca:service name="SCASDOService"
type="com.oracle.test.sdo.HelloSDO" target="sdoHello">
<wlsb:binding.ws
name="mysdosvc"
port="mysdoport" uri="/mysdosvcuri"
databinding="toplink.sdo">
<property name="weblogic.sca.binding.ws.sdoSchemaFile">
MySDO.xsd
</property>
</wlsb:binding.ws>
</sca:service>
To configure Glassfish JAXB databinding, enter glassfish.jaxb as the value for the databinding attribute in the binding.ws element.
An example of GlassFish JAXB binding is shown in Example 8-8, "GlassFish JAXB Databinding".
You can provide an external databinding customization XML file that provides additional information on the Web Service binding. This file provides mapping metadata to define the attributes of a Java Web Service endpoint. The external customization file can be used to customize both WSDL and schema.
One example scenario of the use of the customization file is when the contract class for an SCA service contains overloaded methods that you want to expose as Web Service operations. The customization file can be used to disambiguate operation names for the Web Service.
Another example scenario (schema customization) is to change the name or the order of elements in a generated complex type.
To configure custom databinding:
Create the customization file in the same location as the implementation class file. The schema for the customization file, weblogic-wsee-databinding.xsd, must also be bundled with the application. See WebLogic SCA Databindings Customization Descriptor Schema (weblogic-wsee-databinding.xsd) for the schema.
This schema defines three kinds of XML constructs:
Constructs that are analogous to those in JAX-WS and JSR 181 (Web Services Metadata for the Java Platform). These constructs (a) override or define attributes on the Service Endpoint Interface (SEI) and (b) override or specify information that would normally be part of Java Architecture for XML Binding (JAXB) annotations for the value types used in the interfaces of the SEI.
Additional mapping specifications not available using standard JAX-WS or JAXB annotations, primarily for use with the java.util.Collections API.
References to external JAXB mapping metadata from a Toplink Object-XML (OXM) file. This is only relevant for the toplink.jaxb databinding.
When a construct is the direct analog of a JAX-WS, JSR 181, or JAXB annotation, the schema includes a comment with notation such as:
Corresponding Java annotation javax.jws.WebParam.Mode
In the <property> subelement of <binding.ws>:
Enter weblogic.sca.binding.ws.externalCustomizationFile as the value for the name attribute.
Enter the name of the customization file as the content of the <property> element.
An example of the <property> element configured to point to a customization file is shown below in Example 8-10.
Example 8-9 Customization File Reference
<sca:service name="SCAServiceOverloaded"
type="com.oracle.test.SayHelloOverloaded" target="overloadedHello">
<wlsb:binding.ws"
name="myoverloadedsvcname" port="myoverloadedportname"
uri="/myoverloadedsvcnameuri">
<property
name="weblogic.sca.binding.ws.externalCustomizationFile">overloading_mapping_file.xml
</property>
</wlsb:binding.ws>
</sca:service>
An example of a customization file is shown below in Example 8-10. It shows how an overloaded sayHello() method in the POJO is to be supported. The methods are mapped to two operations in the WSDL called sayHello and sayHelloWithString.
Example 8-10 Databinding Customization File (1)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<java-wsdl-mapping name="com.oracle.test.SayHelloOverloaded"
xmlns="http://xmlns.oracle.com/weblogic/weblogic-wsee-databinding"
xmlns:oxm="http://www.eclipse.org/eclipselink/xsds/persistence/oxm"
databinding="toplink.jaxb">
<java-methods>
<java-method name="sayHello">
<web-method operation-name="sayHello"/>
</java-method>
<java-method name="sayHello">
<web-method operation-name="sayHelloWithString"/>
<java-params>
<java-param java-type="java.lang.String"/>
</java-params>
</java-method>
</java-methods>
</java-wsdl-mapping>
The customization file shown below in Example 8-11 illustrates the use of an inline <toplink-oxm> element to customize the order of elements in the generated schema. This example specifies that the schema generated for the ShoppingCartItem object will contain the quantity, price, and id properties in the specified order instead of the default ordering.
Example 8-11 Databinding Customization File (2)
<java-wsdl-mapping name="com.oracle.test.GetPriceRemote"
xmlns="http://xmlns.oracle.com/weblogic/weblogic-wsee-databinding"
xmlns:oxm="http://www.eclipse.org/eclipselink/xsds/persistence/oxm"
databinding="toplink.jaxb">
<xml-schema-mapping>
<toplink-oxm java-package="com.oracle.test">
<oxm:xml-bindings>
<oxm:xml-schema/>
<oxm:java-types>
<oxm:java-type name="com.oracle.test.ShoppingCartItem">
<oxm:xml-type prop-order="quantity price id"/>
</oxm:java-type>
</oxm:java-types>
</oxm:xml-bindings>
</toplink-oxm>
</xml-schema-mapping>
</java-wsdl-mapping>
Simple Object Access Protocol, (SOAP) attachments are supported when using TopLink/EclipseLink JAXB databinding. These types are supported:
SOAP Message Transmission Optimization Mechanism (MTOM)
SOAP Messages with Attachments (SwA)
To configure databinding for SOAP attachments:
Specify TopLink/EclipseLink JAXB databinding by entering toplink.jaxb as the value for the databinding attribute in the binding.ws element.
Note:
In practice, this step is not necessary, because toplink.jaxb is the default value for databinding. However, you cannot use any other value for databinding.
Configure for MTOM or SwA, as described in the following sections:
Enable MTOM in either of the following ways:
Put an @MTOM annotation on an SEI or contract class, as shown in Example 8-12. This enables MTOM for base64Binary types.
Include a <mtom> element as an immediate child of the <java-wsdl-mapping> element in the external mapping file, as shown in Example 8-13. The attributes for the <mtom> element are optional. The default for enabled is true, and the default for threshold is 0.
The following examples illustrate using an external customization file to enable MTOM on an SCA POJO to be used as a Web Service endpoint:
Example 8-14 shows the Spring context, with a reference to the external customization file mtomCustomizationMapping.xml.
Example 8-15 shows the external customization file mtomCustomizationMapping.xml.
Example 8-16 shows the Java classes for the example.
<sca:service name="SCAMtomService" type="com.oracle.test.SayHelloMtom" target="helloMtom">
<binding.ws
xmlns="http://xmlns.oracle.com/weblogic/weblogic-sca-binding"
name="myMtomSvc"
port="myMtomPort"
uri="/myMtomSvcUri"
databinding="toplink.jaxb">
<property
name="weblogic.sca.binding.ws.externalCustomizationFile">mtomCustomizationMapping.xml
</property>
</binding.ws>
</sca:service>
Example 8-15 External Customization File mtomCustomizationMapping.xml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<java-wsdl-mapping name="com.oracle.test.SayHelloMtom"
xmlns="http://xmlns.oracle.com/weblogic/weblogic-wsee-databinding"
xmlns:oxm="http://www.eclipse.org/eclipselink/xsds/persistence/oxm"
databinding="toplink.jaxb">
<xml-schema-mapping>
<toplink-oxm java-package="com.oracle.test">
<xml-bindings xmlns="http://www.eclipse.org/eclipselink/xsds/persistence/oxm">
<java-types>
<java-type name="com.oracle.test.HasArray">
<java-attributes>
<xml-element java-attribute="arr" xml-mime-type="text/xml" />
</java-attributes>
</java-type>
</java-types>
</xml-bindings>
</toplink-oxm>
</xml-schema-mapping>
<mtom threshold="2"/>
</java-wsdl-mapping>
//SayHelloMtom.java
public class SayHelloMtom {
public HasArray modifyArray(String name, int b) {
HasArray ha = new HasArray();
ha.b = b;
ha.arr = ("<?xml version='1.0' ?><z>" + name + "</z>").getBytes();
return ha;
}
}
//HasArray.java
package com.oracle.test;
public class HasArray {
public byte[] arr = "<?xml version='1.0' ?><xy/>".getBytes();
public int b = 5;
}
The SwA attachment type SwaRef is supported in two ways:
Use the @XmlAttachmentRef annotation on a DataHandler type parameter and/or return type, as shown in Example 8-17.
Use the xml-attachment-ref attribute in the external customization file, as shown in Example 8-18. This example, along with Example 8-19 (the Spring context) and Example 8-20 (the Java classes) show SwA enabled on an SCA POJO to be used as a Web Service endpoint.)
Example 8-18 External Customization File swaCustomizationMapping.xml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<java-wsdl-mapping name="com.oracle.test.SayHelloSwa"
xmlns="http://xmlns.oracle.com/weblogic/weblogic-wsee-databinding"
xmlns:oxm="http://www.eclipse.org/eclipselink/xsds/persistence/oxm"
databinding="toplink.jaxb">
<xml-schema-mapping>
<toplink-oxm java-package="com.oracle.test">
<xml-bindings xmlns="http://www.eclipse.org/eclipselink/xsds/persistence/oxm">
<java-types>
<java-type name="com.oracle.test.HasDataHandler">
<java-attributes>
<xml-element java-attribute="data" xml-attachment-ref="true" />
</java-attributes>
</java-type>
</java-types>
</xml-bindings>
</toplink-oxm>
</xml-schema-mapping>
</java-wsdl-mapping>
Example 8-19 Spring Context with Reference to External Customization File
<sca:service name="SCAMtomService" type="com.oracle.test.SayHelloSwa" target="helloSwa">
<binding.ws
xmlns="http://xmlns.oracle.com/weblogic/weblogic-sca-binding"
name="mySwaSvc"
port="mySwaPort"
uri="/mySwaSvcUri"
databinding="toplink.jaxb">
<property
name="weblogic.sca.binding.ws.externalCustomizationFile">swaCustomizationMapping.xml
</property>
</binding.ws>
</sca:service>
//SayHelloSwa.java
package com.oracle.test;
public class SayHelloSwa {
public HasDataHandler echoDataHandler(HasDataHandler dh) {
return dh;
}
}
//HasDataHandler.java
package com.oracle.test;
import javax.activation.DataHandler;
public class HasDataHandler {
public DataHandler data;
}
An alternative to using a wrapper class like the HasDataHandler class shown in Example 8-20 is to use the DataHandler as a parameter to the Web Service directly. To do so, modify the customization file as shown in Example 8-21:
Example 8-21 Customization File Using a DataHandler as a Parameter to a Web Service
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<java-wsdl-mapping name="com.oracle.test.SayHelloSwa"
xmlns="http://xmlns.oracle.com/weblogic/weblogic-wsee-databinding"
xmlns:oxm="http://www.eclipse.org/eclipselink/xsds/persistence/oxm"
databinding="toplink.jaxb">
<java-methods>
<java-method name="echoDataHandler">
<java-params>
<java-param>
<oxm:xml-element xml-attachment-ref="true" xml-mime-type="text/xml"/>
</java-param>
</java-params>
</java-method>
</java-methods>
</java-wsdl-mapping>
The corresponding SayHelloSwa.java file is shown in Example 8-22.
//SayHelloSwa.java
package com.oracle.test;
import javax.activation.DataHandler;
import javax.mail.util.ByteArrayDataSource;
public class SayHelloSwa {
public DataHandler echoDataHandler(DataHandler dh) {
byte[] b = new byte[1024];
try {
int len = dh.getInputStream().read(b);
String resp = "<swarefresponse>" + new String(b,0,len) + "</swarefresponse>";
return new DataHandler(new ByteArrayDataSource(resp.getBytes(), "text/xml"));
} catch (Exception e) {
String err = "<err>An error occurred: " + e.getClass().getName() + " - " + e.getMessage() + "</err>";
return new DataHandler(new ByteArrayDataSource(err.getBytes(), "text/xml"));
}
}
}
s
Java Collection and Map objects are supported when using TopLink/EclipseLink JAXB databinding.
Note:
Built in Java subclasses of java.util.List and java.util.Map are supported. Multi-dimensional support (that is, Array of Arrays, Array of HashMaps, List of Lists, etc) will be supported in a future release
You can express the generics type argument of a Collection (or members of the Collection family) with either an annotation or an external mapping file. For example, the two methods in the interface shown in Example 8-23 are equivalent in their input types if the processItems2 method uses the external mapping file shown in Example 8-24.
Example 8-23 Methods in an Interface (1)
public interface CollectionProcessor {
public String processItems1(Collection<ItemType> items);
public String processItems2(Collection items);
}
Example 8-24 shows the fragment of the external mapping file for the processItems2 method shown in Example 8-23.
Example 8-24 External Mapping File for Configuring Collection Objects [1]
<java-method name="processItems2">
<java-params>
<java-param>
<oxm:xml-element type="mypackage.ItemType"/>
</java-param>
</java-params>
</java-method>
Example 8-25 shows another example of an external mapping file for configuring Collection objects.
Currently, externalizing the generic types is not directly supported for java.util.Map types.
However, if it is not possible to specify the generic type for the Map directly in the Java class, it can be indirectly supported by using the Java XML type adapter feature of the toplink.jaxb binding. This involves writing custom serializers for the desired generic Map types and specifying the custom serializers in the external mapping file, as shown in Example 8-26, Example 8-27, and Example 8-28.
Example 8-26 POJO to be Exposed as a Web Service (Without Generic Types on the Map)
//Implementation class
public class CollectionMapExtTypeArgImpl {
public Map testMapOfCustomAdapters(Map map) {
//implementation goes here
}
}
Example 8-27 Custom Adapter Classes
//Custom Adapter class for Map<String, Integer> (JAXB Xml Adapter)
public class MapStringIntegerAdapter extends XmlAdapter<MapStringInteger, HashMap> {
public HashMap unmarshal(MapStringInteger m) throws Exception {
HashMap map = new HashMap();
for (StringIntegerEntry e: m.entry) map.put(e.key, e.value);
return map;
}
public MapStringInteger marshal(HashMap m) throws Exception {
MapStringInteger map = new MapStringInteger();
map.entry = new ArrayList<StringIntegerEntry>();
for (Object k: m.keySet()) {
StringIntegerEntry e = new StringIntegerEntry();
e.key = (String) k;
e.value = (Integer) m.get(k);
map.entry.add(e);
}
return map;
}
}
//MapStringInteger.java
public class MapStringInteger {
public static class StringIntegerEntry {
@XmlAttribute
public String key;
@XmlValue
public Integer value;
}
public List<StringIntegerEntry> entry;
}
//Similar implementation for MapStringCustomerAdapter would be needed
Example 8-28 Customization file fragment showing return type of Map<String, Integer> and parameter type of Map<String, Customer>
<java-method name="testMapOfCustomAdapters">
<oxm:xml-element xmlns='http://www.eclipse.org/eclipselink/xsds/persistence/oxm'>
<oxm:xml-java-type-adapter value='com.oracle.test.MapStringIntegerAdapter'/>
</oxm:xml-element>
<java-params>
<java-param>
<oxm:xml-element xmlns='http://www.eclipse.org/eclipselink/xsds/persistence/oxm'>
<oxm:xml-java-type-adapter value='com.oracle.test.MapStringCustomerAdapter'/>
</oxm:xml-element>
</java-param>
</java-params>
</java-method>
Several configuration settings can be specified in more than one place, including databinding mode, SOAP version, target namespace, service name, and port name. If one of those settings is specified in multiple places, they are evaluated in the following order of precedence:
If a configuration option is specified (and is not empty) in the Spring context in the binding.ws configuration, that setting is used. This setting takes precedence over all others.
If a configuration option is not specified in the Spring context in the binding.ws configuration, the value in the external customization file is used. This setting takes precedence over 3, below.
If a configuration option is not specified in the Spring context or the external customization file but is specified in annotations on the POJO, the annotations on the POJO are used.
At deployment, WebLogic SCA Runtime:
Uses the service interface information to generate a WSDL.
Publishes the service at the specified URI (relative to the context root) as a JAX-WS endpoint.
The runtime behavior of Web Service bindings is described below.
Requests to services are handled as follows:
The appropriate data binding converts the incoming SOAP message payload into Java objects.
Any policies are handled by the JAX-WS runtime.
The POJO implementing the service is invoked by the WebLogic SCA Runtime.
WebLogic SCA Runtime recognizes that a reference invocation is for an external reference. It acts as a JAX-WS client to the external Web Service, unmarshals the result to Java and returns it in a manner transparent to the calling Java code.