Standard Java Class Deployment Descriptor
A deployment descriptor which exposes a service which is implemented via a standard Java class (including a normal Java Bean) looks like the following:<isd:service xmlns:isd="http://xml.apache.org/xml-soap/deployment"
id="urn:service-urn" [type="message"] [checkMustUnderstands="true|false"]> <isd:provider type="java" scope="Request | Session | Application" methods="exposed-methods"> <isd:java class="implementing-class" [static="true|false"]/> </isd:provider> <isd:faultListener>org.apache.soap.server.DOMFaultListener</isd:faultListener>
</isd:service>!!!!!!!!!!!!!!!!!!!!!!!!!
Where service-urn is the URN that you want to give to a service, exposed-methods is a space separated list of methods which you wish to expose, and implementing-class is fully qualified class name (i.e. packagename.classname) that provides the methods which are being exposed.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!On the <service> element, there is an optional attribute called type which may be set to the value "message" if the service is document-oriented instead of being an RPC invoked service, and an optional attribute called checkMustUnderstands which may be set to either "true" or "false" depending upon whether or not you want the server to throw a Fault if there were SOAP headers in the request which were ed as MustUnderstand. On the <java> element, there is an optional attribute called static, which may be set to either "true" or "false", depending upon whether or not the methods which are being exposed are static or not. The <provider> element also takes a scope attribute which indicates the lifetime of the instantiation of the implementing class. "Request" indicates that the object will be removed after this request has completed, "Session" indicates that the object will last for the current lifetime of the HTTP session, and Application indicates that the object will last until the servlet which is servicing the requests is terminated.
A deployment descriptor which exposes a service which is implemented via a standard Java class (including a normal Java Bean) looks like the following:<isd:service xmlns:isd="http://xml.apache.org/xml-soap/deployment"
id="urn:service-urn" [type="message"] [checkMustUnderstands="true|false"]> <isd:provider type="java" scope="Request | Session | Application" methods="exposed-methods"> <isd:java class="implementing-class" [static="true|false"]/> </isd:provider> <isd:faultListener>org.apache.soap.server.DOMFaultListener</isd:faultListener>
</isd:service>!!!!!!!!!!!!!!!!!!!!!!!!!
Where service-urn is the URN that you want to give to a service, exposed-methods is a space separated list of methods which you wish to expose, and implementing-class is fully qualified class name (i.e. packagename.classname) that provides the methods which are being exposed.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!On the <service> element, there is an optional attribute called type which may be set to the value "message" if the service is document-oriented instead of being an RPC invoked service, and an optional attribute called checkMustUnderstands which may be set to either "true" or "false" depending upon whether or not you want the server to throw a Fault if there were SOAP headers in the request which were ed as MustUnderstand. On the <java> element, there is an optional attribute called static, which may be set to either "true" or "false", depending upon whether or not the methods which are being exposed are static or not. The <provider> element also takes a scope attribute which indicates the lifetime of the instantiation of the implementing class. "Request" indicates that the object will be removed after this request has completed, "Session" indicates that the object will last for the current lifetime of the HTTP session, and Application indicates that the object will last until the servlet which is servicing the requests is terminated.
With the Apache-SOAP Administration Tools it is possible to use a Web browser to deploy and un-deploy services and to review the list and the definitions of the services deployed on a given SOAP server.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Point your browse to http://hostname:port/soap/admin (see above) and you will get the "Apache-SOAP Admin" screen with three options:
！！！！！！！！！！！！！！！！！！！！！！Deploy to deploy a new service.
Un-deploy to remove a deployed service.
List shows the list of services currently deployed in the server.
The usage of these functions is immediate once one understands the nature of the information required for deploying a service. In the next section we describe this information.
/*
however what soap do, I suggest using Apache Axis instead of Apache SOAP.
Apache Axis is a more useful and convenient implementing tools of soap
the address: http://ws.apache.org/axis/
*/
Mother said: "you need get more point back".