A client application invoking a service can need custom persistent configuration in addition to the extended default configuration that is specified in the deployment descriptor. You can add custom configurations for interceptors, handlers, transports, serializers, etc.

This part of the configuration is available via an extensible WSO2 SOA Enablement Server configuration framework, which is used the same way for a client as for a Web service. See Custom Configuration in Writing Web Services for more information, and Client Settings for a discussion of the client-side classes.

Example 94 shows the custom client-side configuration of a transport (elements <jumbo:port> and <jumbo:timeout>).

	Note
	Extended configuration elements must be in a different namespace than the package namespace.

<package name="jumbo_transport"
  xmlns="http://wso2.com/wasp/package/1.2"
  targetNamespace="http://wso2.com/example/transport/jumbo/"
  version="1.0">
  <documentation url="http://www.wso2.com/">
      <display-name>JUMBO Transport</display-name>
      <description>JUMBO Transport</description>
      <small-icon>http://www.wso2.com/images/logo_others.gif</small-icon>
  </documentation>
  <transport name="jumbo"
     scheme="jumbo"
     implementation-class="example.processing.transport.JumboTransport"
     preload="false"
     default-server="true"
      xmlns:jumbo="http://wso2.com/example/transport/jumbo/">
      <jumbo:port>2929</jumbo:port>
      <jumbo:timeout>40000</jumbo:timeout>
   </transport>
</package>

The important information is that extended configuration elements must be in a different namespace than the package namespace. In the example above, the extended elements are in the namespace xmlns:jumbo="http://wso2.com/example/transport/jumbo/" and the package namespace is xmlns="http://wso2.com/wasp/package/1.2"