org.apache.soap.util
Interface ConfigManager

All Known Implementing Classes:

BaseConfigManager, DefaultConfigManager, XMLConfigManager

public interface ConfigManager

A ConfigManager ...

Author:

Dug (dug@us.ibm.com) With the introduction of a ConfigManager, the notion of a SOAP configuration file was also introduced. The SOAP server will now look for a 'soap.xml' file - or whatever filename was specified by the 'ConfigFile' init parameter of the Servlet. The soap.xml file should look like: See 'DefaultConfigManager' for more info. Classes that implement these APIs are responsible for saving and loading the list of deployed services. The SOAP server will just call deploy/undeploy... and its up to the class that implements these API to handling the persistence of the list. See the DefaultConfigManager to see an example of how to do this. Init will be called after the 'setOptions' call allowing the ConfigMgr to do any setup.

Method Summary

void	deploy(DeploymentDescriptor dd)
void	init()
java.lang.String[]	list()
DeploymentDescriptor	query(java.lang.String id)
void	setContext(javax.servlet.ServletContext context)
void	setOptions(java.util.Hashtable options)
DeploymentDescriptor	undeploy(java.lang.String id)

Method Detail

setContext

public void setContext(javax.servlet.ServletContext context)

setOptions

public void setOptions(java.util.Hashtable options)
                throws SOAPException

init

public void init()
          throws SOAPException

deploy

public void deploy(DeploymentDescriptor dd)
            throws SOAPException

list

public java.lang.String[] list()
                        throws SOAPException

undeploy

public DeploymentDescriptor undeploy(java.lang.String id)
                              throws SOAPException

query

public DeploymentDescriptor query(java.lang.String id)
                           throws SOAPException