WSDD

All of the required values are passed to the Axis runtime in the form of a file with the extension . wsdd.

Instead, we inline the code into the deployment descriptor, as shown in the e4xstock. wsdd file in the samples for this article.

Optionally repackage the service-config. wsdd back into the war file for future deployment.

Add the lines shown in Listing 8 to server. wsdd at the service level.

The deployment descriptor used in step 1 (deployAxisSQ. wsdd) is shown in Listing 12.

Step 2 of the list above uses the deployment descriptor deployAxisClient. wsdd, shown in Listing 13.

Meet the experts is a monthly feature on the developerWorks WebSphere Web site.

Step 2 uses deployAxisClientX. wsdd, the deployment descriptor shown in Listing 19.

This should only be done at deployment so that if the Axis engine changes a new service-config. wsdd deployment descriptor can be generated.

This is done by passing the deploy. wsdd file to the Axis administrator task to deploy the web service.

You can see this in the e4xstockEnv. wsdd sample file.

Now you can set up your Axis installation for deployment on Geronimo, packaged with your Axis Web service. Create the server-config. wsdd

Listing 3 shows a typical wsdd file used for deploying services into Axis. It shows that a custom provider will handle incoming requests

java. lang. Exception: WSWS3352E: Error: Couldn't find a matching Java operation for WSDD operation