\section{Axis\-C++ Compound List}
Here are the classes, structs, unions and interfaces with brief descriptions:\begin{CompactList}
\item\contentsline{section}{{\bf Admin\-Utils} (This class contains the Server side administration functionalities)}{\pageref{classAdminUtils}}{}
\item\contentsline{section}{{\bf Any\-Element} (Struct that represents any XML element)}{\pageref{structAnyElement}}{}
\item\contentsline{section}{{\bf Any\-Type} }{\pageref{structAnyType}}{}
\item\contentsline{section}{{\bf Attribute} (Interface for the Attribute class)}{\pageref{classAttribute}}{}
\item\contentsline{section}{{\bf Axis\-Config} (Class for taking configuration parameters)}{\pageref{classAxisConfig}}{}
\item\contentsline{section}{{\bf Axis\-Exception} (Base class for Axis C++ exception hierarchy)}{\pageref{classAxisException}}{}
\item\contentsline{section}{{\bf Axis\-File} (Class for allocating file resources for Axis C++)}{\pageref{classAxisFile}}{}
\item\contentsline{section}{{\bf Axis\-IOStream} (Interface of the input/output stream of Axis transport. ISOAPTransport is derived from this interface)}{\pageref{classAxisIOStream}}{}
\item\contentsline{section}{{\bf Axis\-Time} (Time manipulating helper class)}{\pageref{classAxisTime}}{}
\item\contentsline{section}{{\bf Axis\-Trace} (This is class is used to log messages when AXISTRACE is defined)}{\pageref{classAxisTrace}}{}
\item\contentsline{section}{{\bf Character\-Element} (Interface for the Character\-Element class)}{\pageref{classCharacterElement}}{}
\item\contentsline{section}{{\bf Complex\-Element} (Interface for the Complex\-Element class)}{\pageref{classComplexElement}}{}
\item\contentsline{section}{{\bf Handler} (Interface for handlers)}{\pageref{classHandler}}{}
\item\contentsline{section}{{\bf Handler\-Base} (Interface for the Handlers. This is the base class for: -{\bf Handler} {\rm (p.\,\pageref{classHandler})} -{\bf Wrapper\-Class\-Handler} {\rm (p.\,\pageref{classWrapperClassHandler})} In the Axis Architecture there are different types of Handlers : -NORMAL\_\-HANDLER : A {\bf Handler} {\rm (p.\,\pageref{classHandler})} which is used to process SOAP Headers. -WEBSERVICE\_\-HANDLER : A web service is also considered as a {\bf Handler} {\rm (p.\,\pageref{classHandler})}. -CHAIN\_\-HANDLER : {\bf Handler} {\rm (p.\,\pageref{classHandler})} Chains are also derived from {\bf Handler} {\rm (p.\,\pageref{classHandler})}. Each of these handlers will inherit from this Handler\-Base which serves as the base point for all the different types of Handlers)}{\pageref{classHandlerBase}}{}
\item\contentsline{section}{{\bf IAdmin\-Utils} (This Interface contains the Server side administration functionalities)}{\pageref{classIAdminUtils}}{}
\item\contentsline{section}{{\bf IHandler\-Soap\-Serializer} (Interface for the IHandler\-Soap\-Serializer class. This interface is exposed to a {\bf Handler} {\rm (p.\,\pageref{classHandler})} Writer, to let him manipulate on the Serialzer object. Example usage is given below)}{\pageref{classIHandlerSoapSerializer}}{}
\item\contentsline{section}{{\bf IHeader\-Block} (Interface for the IHeader\-Block class)}{\pageref{classIHeaderBlock}}{}
\item\contentsline{section}{{\bf IWrapper\-Soap\-De\-Serializer} (Interface for the IWrapper\-Soap\-De\-Serializer class)}{\pageref{classIWrapperSoapDeSerializer}}{}
\item\contentsline{section}{{\bf Soap\-Header} (The Header element information item according to SOAP 1.2 specification)}{\pageref{classSoapHeader}}{}
\item\contentsline{section}{{\bf Soap\-Serializer} (Interface for the Soap\-Serializer class)}{\pageref{classSoapSerializer}}{}
\item\contentsline{section}{{\bf SOAPTransport} (Interface of any Axis transport layer)}{\pageref{classSOAPTransport}}{}
\item\contentsline{section}{{\bf Stub} (This is the client Stub base class to be inherited by all stub classes genarated by WSDL2WS tool. This class acts as the interface between the users and the Axis C++ engine (client side). Programmer can use the API defined here to enrich the client application functionality. Setting transport properties, setting SOAP headers, setting connection timeout and specifying a proxy on the client stub is facilitated with this interface)}{\pageref{classStub}}{}
\item\contentsline{section}{{\bf Stub\-Functions} (Structure with function pointer definitions to provide {\bf Stub} {\rm (p.\,\pageref{classStub})} base class's functionalities for C stubs)}{\pageref{structStubFunctions}}{}
\item\contentsline{section}{{\bf Type\-Mapping} (Interface for the Type\-Mapping class)}{\pageref{classTypeMapping}}{}
\item\contentsline{section}{{\bf Wrapper\-Class\-Handler} }{\pageref{classWrapperClassHandler}}{}
\item\contentsline{section}{{\bf WSDDHandler} (Interface for the WSDDHandler class)}{\pageref{classWSDDHandler}}{}
\item\contentsline{section}{{\bf WSDDService} (Interface for the WSDDService class)}{\pageref{classWSDDService}}{}
\item\contentsline{section}{{\bf XMLParser} (Interface that any parser wrapper should implement in order to be use in Axis as a XML PULL parser. This interface basically describes XML pull parsing behavior. Any SAX or DOM parser can be wrapped to expose XML pull behavior by implementing this interface. But the efficiency of the overall component depends on the particular implementaion. Its the responsibility of the implementation class to free any memory allocated inside the class. The class should not deallocate the given input stream)}{\pageref{classXMLParser}}{}
\item\contentsline{section}{{\bf xsd\_\-\_\-base64Binary} }{\pageref{structxsd____base64Binary}}{}
\item\contentsline{section}{{\bf xsd\_\-\_\-hex\-Binary} }{\pageref{structxsd____hexBinary}}{}
\end{CompactList}
