Human-readable DeployedServices.ds

[Magnús Þór Torfason <ma...@handtolvur.is>]

I have been trying to get the hang of apache soap for some time now, but am
unable to grasp server configuration.

All the demonstration code assumes that services are deployed from the
client, which uses a very neat DeploymentDescriptor.xml file to configure
the service.

At the server end, this info is written into a binary DeployedServices.ds
file, that is impossible to modify.

I cannot imagine that this is the typical way to configure services.  I
would think that two methods would be most often used:

1) Configuration using a text file, such as the DeploymentDescriptor.xml,
located at the server.

2) Deployment controlled from the server (so that some other subsystem can
determine which services are available and deploy soap listeners for the
available services).

I have been unable to find examples of either.  Please advice.

Regards,

Magnus


---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org