Axis1 simple tutorial

Axis

1. Direct deployment of instante deployment is to change a written java file. place the jws extension in the axis project root directory, and axis will compile the jws into a class file of the same name at startup and put it under the axis/WEB-INF/export sclasses directory, then you can use .... axis/file name. jws? To access the wsdl representation of the deployment.

Direct deployment requires that the jws file be placed directly without the package path, which is useless.

 

2. customizes the publishing of M deployment, and customizes the publishing content using the wsdd (Web Service Deployment Descriptor) file. This is used in actual applications.

Similar to deploying a project under Tomcat, place the entire directory after the webservice project is compiled under axis/WEB-INF/classes, and write the corresponding wsdd deployment file under axis/WEB-INF.

Wsdd compiled by myself is only used to generate standard configuration files, such:

<Deployment xmlns = "http://xml.apache.org/axis/wsdd/" <br/> xmlns: java = "http://xml.apache.org/axis/wsdd/providers/java"> <br/> <service name = "Counter" provider = "java: RPC "> <br/> <parameter name =" className "value =" gss. test. counter "/> <br/> <parameter name =" allowedMethods "value =" * "/> <br/> </service> <br/> </deployment>

 

Then in CMD mode, switch to axis/WEB-INF to execute the command

Java-Djava. ext. dirs = lib org. apache. axis. client. AdminClient deploy. wsdd

If the following information is displayed:

Processing file deploy. wsdd
<Admin> Done processing </Admin>

The wsdd is edited successfully, and the edited file contains information about the entire axis service for the server-config.wsdd, including the previous deploy. wsdd information.

 

Then, Use http: // url: port/axis/webservices/servicename to access the published service.