feedback and requirements on axis c

[Jaspreet Singh <Ja...@quark.co.in>]

Hi All

I am using Axis C and i've come across situations where i would have
certainly liked Axis to be more flexible and extensible to suit my needs.
This can be considered as a set of requirements from my side.

1. The server picks up the information about the services and the methods it
wants to expose from a deployment descriptor (wsdd) file. It would be great
if you could provide a separate interface to register and unregister
services at runtime.

2. The services are deemed to be separate dynamic libraries. There should be
an interface to register the web service functions at runtime so that there
is no restriction for the client to generate a separate dll file. The client
can register a function pointer for methods of the service to be invoked.

3. The code for the transport layer (Sender, Receiver, Transport classes in
the client lib and separate functions in the sample server) should be put in
a separate lib and the same interface should be used for consistency. it
would be easier for clients to switch to another transport library if need
be.


TIA
Jaspreet