InfoCenter Home > 4.8.2.1: SOAP deployment descriptors in WebSphere Application ServerThis article describes the different types of deployment
descriptors that can be used in WebSphere Application Server.
Deployment descriptors for each of the soap samples are included
in the soapsamples.ear file in the ServerSamplesCode directory
(for example, Standard Java class deployment descriptorA deployment descriptor which exposes a service that is implemented with a standard Java class (including a normal java bean) looks like this example: <isd:service xmlns:isd="http://xml.apache.org/xml-soap/deployment" id="urn:service-urn" [type="message"]> <isd:provider type="java" scope="Request | Session | Application" methods="exposed-methods"> <isd:java class="implementing-class" [static="true|false"]/> </isd:provider> where:
On the <service> element, there is an optional attribute called type which is set to the value "message" if the service is document-oriented instead of RPC-invoked. On the <java> element, there is an optional attribute called static, which may be set to either "true" or "false", depending on whether the methods are exposed or not exposed. If exposed, this attribute indicates whether the method is static or not static. On the <provider> element, there is a scope attribute which indicates the lifetime of the instantiation of the implementing class.
EJB deployment descriptorA deployment descriptor that exposes a service which is implemented with an Enterprise Java Bean looks like this next example: <isd:service xmlns:isd="http://xml.apache.org/xml-soap/deployment" id="urn:service-urn"> <isd:provider type="provider-class" scope="Application" methods="exposed-methods"> <isd:option key="JNDIName" value="jndi-name"/> <isd:option key="FullHomeInterfaceName" value="home-name" /> </isd:provider> <isd:faultListener>org.apache.soap.server.DOMFaultListener</isd:faultListener> </isd:service>
A description of the keys and variables follows:
Bean Scripting Framework (BSF) script deployment descriptorA deployment descriptor that exposes a service which is implemented with a BSF script looks like the following example: <isd:service xmlns:isd="http://xml.apache.org/xml-soap/deployment" id="urn:service-urn"> <isd:provider type="script" scope="Request | Session | Application" methods="exposed-methods"> <isd:script language="language-name" [source="source-filename"]>[script-body] </isd:script> </isd:provider> <isd:faultListener>org.apache.soap.server.DOMFaultListener</isd:faultListener> </isd:service> where:
The deployment descriptor must also have a source attribute on the <script> element, or a script-body attribute. The script-body attribute contains the actual script that is used to provide the service. If the deployment descriptor has the source attribute, then source-filename refers to the file which contains the service implementation. DB2 stored procedure deployment descriptorA deployment descriptor which exposes one or more DB2 stored procedures as a services looks like the following example: <isd:service xmlns:isd="http://xml.apache.org/xml-soap/deployment" id="urn:service-urn"> <isd:provider type="com.ibm.soap.providers.WASDB2SPProvider" scope="Application" methods="* | exposed-methods"> <isd:option key="userID" value="db-userid"/> <isd:option key="password" value="db-password"/> [<isd:option key="fullContextFactoryName" value="context-factory"/> <isd:option key="datasourceJNDI" value="jndi-name"/>] [<isd:option key="dbDriver" value="db-driver"/> <isd:option key="dbURL" value="db-url"/>] </isd:provider> <isd:faultListener>org.apache.soap.server.DOMFaultListener</isd:faultListener> </isd:service> where:
The methods attribute on the <provider> element can contain a list of space separated procedure names to expose, or an "*" (asterisk). An asterisk indicates all available stored procedures should be exposed. See the related topics section for links to an enablement scenario. |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|