For the invocation on the qos and key objects please refere to the APIs for

org::xmlBlaster::util::qos (for ConnectQos)

org::xmlBlaster::client::qos

org::xmlBlaster::client::key

Below you find an example for a typical C++ client connecting to xmlBlaster.
In the configuration section there is a list of operating systems and
CORBA libraries which are tested with xmlBlaster. Other combinations should
work out of the box or with minor changes. Optionally you can use our native
SOCKET protocol instead of CORBA to access the server.

Besides the orbs mentioned in the table the source code is already prepared for other corba vendors such as

ORBACUS

but the current status of the library has not been tested against these orbs.
See CompatibleCorba.h for a current list.

Please let us know if you successfully compiled and ran the testsuite with other combinations.
Particularly interesting it would be the INTEL compiler on Linux and Windows and Solaris with the GCC Compiler.

How to check to the version of the library

To check which version your shared library is (UNIX only) try one of the following:

cd xmlBlaster/lib
# Searching manually the lib:
strings libxmlBlasterClient.so | grep Global.cpp
# Or using the what command:
what libxmlBlasterClient.so
# Or (ident is part of the RCS package):
ident libxmlBlasterClient.so
# The result is something like:
Global.cpp,v 1.29 2003/03/02 19:53:42 ruff Exp
# You can now lookup Global.cpp 1.29 with
cd xmlBlaster/src/c++/util
svn log Global.cpp

How to create the Doxygen documentation

If you want to generate the documentation yourself
you need to install Doxygen and GraphViz as described in their manuals.
Than create the documentation like that:

cd $XMLBLASTER_HOME/src/c++/doc
doxygen Doxyfile

Now you can point your browser on
$XMLBLASTER_HOME/doc/doxygen/cpp/html/index.html to view the documentation.

After setting export MANPATH=:$XMLBLASTER_HOME/doc/doxygen/c/man:$XMLBLASTER_HOME/doc/doxygen/cpp/man
you are ready to read the manual pages with for example 'man XmlBlasterAccess' or 'man 3 Global'.

NOTE: Configuration parameters are specified on command line (-someValue 17) or in the
xmlBlaster.properties file (someValue=17). See requirement "util.property" for details.
Columns named Impl tells you if the feature is implemented.
Columns named Hot tells you if the configuration is changeable in hot operation.