Registering custom transports

[Tim Kettler <ti...@udo.edu>]

Hi,

we are currently developing a custom transport for Axis 1.2, using the
JXTA peer framework.

We already figured out how to add a transport (along with the
appropriate sender class) to the EngineConfiguration and have
successfully registered a custom protocol (jxta://...).

However, at some point it seems to be necessary to do something like:

(step 1)
Call.addTransportPackage("edu.udo.kinjo.common.transport");
Call.setTransportForProtocol("jxta", JXTATransport.class);

and later on

(step 2)
_call.setTransport(new JXTATransport());

on the concrete call instance.

Is there a way to let Axis figure out automatically which transport to
use, depending on the given endpoint URL, making at least the second
step obsolete? Furthermore, can step 1 be done via the engine
configuration (a WSDD, that is)? All examples seem to set this in the
source code...

Thanks in advance.

Regards,
Tim Kettler