The Server-Side Pad

by Fabien Tiburce, Best practices and personal experiences with enterprise software

SOAP – Apache Axis – Part 2

leave a comment »

In a previous post, we discussed the ease of implementation of jws-based web services. In this post, I want to look at the flip side of this argument: deploying wsdd-based web services is more flexible and powerful yet only marginally more complex.

The file server-config.wsdd located in the application’s WEB-INF directory allows the developer to expose a class as a web service. Just like jws-based services, an existing class can easily be retrofitted and exposed as a web service. Unlike jws-based services, the class is compiled at design time (not run time) and can be packaged. But the superiority of this methodology mostly lies in the use of “handler” classes which can be assigned to the request or response flow of the web service. A handler is a class that does pre-processing or post-processing on the web service. A handler might be used to log the service’s activity of maintain state for example.

While a wsdd-based web service is marginally more complex than a jws-based web service, it allows behaviours to be easily added declaratively to the service definition. Developers are encouraged to use wsdd-based web services for any critical or sensitive operation.


Written by Compliantia

November 14, 2006 at 8:49 pm

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: