Axis client-config.wsdd help

[Anthony Campbell]

Hi guys,

I'm having a little trouble. We intend to use our client stubs for a variety of functionality. However, each feature which intends to use them may have their own configuration (i.e. their own handler etc). At the moment we are using the default client-config.wsdd file:

<?xml version="1.0" encoding="UTF-8"?>
<deployment name="ClientConfig"
            xmlns="http://xml.apache.org/axis/wsdd/"
            xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
 
 <transport name="http" pivot="java:my.custom.package.AxisHandler" />
 <transport name="local" pivot="java :-o	 rg.apache.axis.transport.local.LocalSender" />
 <transport name="java" pivot="java :-o	 rg.apache.axis.transport.java.JavaSender" /> 
</deployment>

This works fine. Moving forward I would like to create this config file dynamically (perhaps based on the feature requirements). Using the following code I get Sax exceptions, which implies I'm not writing the configuration correctly. I was wondering if someone could have a look at the following code. I'm trying to replicate the above xml based config which works fine:

WSDDDeployment deployment = new WSDDDeployment();

//Add Axis transport Handlers
WSDDTransport httpTransport = new WSDDTransport();
httpTransport.setName(HTTPTransport.DEFAULT_TRANSPORT_NAME);
httpTransport.setQName(new QName("my.custom.package.AxisHandler"));
httpTransport.setPivotQName(new QName("my.custom.package.AxisHandler"));
 
WSDDTransport localTransport = new WSDDTransport();
localTransport.setName(new LocalTransport().getTransportName());
localTransport.setPivotQName(new QName("org.apache.axis.transport.local.LocalSender"));
 
WSDDTransport javaTransport = new WSDDTransport();
javaTransport.setName(new JavaTransport().getTransportName());
javaTransport.setPivotQName(new QName("org.apache.axis.transport.java.JavaSender"));
 
deployment.deployTransport(httpTransport);
deployment.deployTransport(localTransport);
deployment.deployTransport(javaTransport);

Kind regards,
Heartless_King

[Peer Reynders]

Before you go too deep down this path ...

Have you actually tested that changing the deployment file during various points at runtime actually has the desired effect?

What you need is a designed test scenario that forces you to swap files - preferrably at different times for all the different reasons that have already been projected. Then you design the files by hand and simply copy the necessary file over the active file when needed. If everything works as hoped you can implement your dynamic system. I wouldn't be surprised it the test might uncover that the file overwriting approach does not work (in memory configuration cache, though there may be a way to force a reload). If all else fails you may have to make the configuration adjustments through the programmatic API.

[Anthony Campbell]

Thanks Peer,

We were keen to avoid the overheard of my managing different deployment files. Ill take a look into your recommendations and keep you posted.

Regards,
King