CASL Web Services framework have just one parameter in common configuration file: name of Web Service config file ;). Why - becouse view of configuration as set of pairs is quite limited in usage.
So, CASL Web Services Config file is 'plain' XML file, does not binded to some DTD - DTD-s are extensible and interpretation of Web Service XML Config is the work of application programmer: he receive SDOM node as configuration for servlet.
It's XML file with main node
WebService, which must consists
from subnodes of type
<?xml version="1.0"> <!-- configuration file for our web service --> <WebService> <Servlet Name="QQQ" Library="libexec/CASL/Web/libQQQ.so" > .... (Some XML fragment, passed to servlet 'QQQ' as SDOM node) ... </Servlet> <Servlet Name="Xxx" Library="libexec/CASL/Web/libXxx.so"> .... (Some XML fragment, passed to servlet 'Xxx' as SDOM node) ... </Servlet> </WebService>
As you see,
Servlet nodes must have 2 attributes:
Name, as you know, is a name of servlet, library -
location of shared library in which this servlet is implemented.
ModCbroker framework, so you must include CORBA Service before Web Service in CASL config file and initialize one [CORBA Service] as server. (i. e. ClientOnly property must be setted ti false).