axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Hawkins (JIRA)" <>
Subject [jira] Commented: (AXISCPP-426) Programmatic configuration
Date Tue, 31 May 2005 15:55:52 GMT
     [ ]
John Hawkins commented on AXISCPP-426:

Some comments from the community ->

A couple of minor suggestions

a) ClientLogPath

Might be nice if you could pass a file_handle so the output could go to
places like sdtout or stderr

b) ClientWSDDFile

Might be nice if you could pass a file_handle so the input could come
places like stdin

Might also be nice if one could optionally pass the equivalent of the file
contents in as a string, rather than just a file name. The program could
then build up the configuration programmatically removing the need for
deploying a separate file.

c) Library names

Might be nice if all the library names on the different platforms had a
standardised naming convention like
HTTP_channel.dll and, then you could have the
axiscpp.conf and the api take a short form of the shared library name, so
the method setHTTPChannelLibrary("HTTP_channel"); would be platform neutral
and the client would look for HTTP_channel.dll on the PATH on Windows or on the LD_LIBRARY_PATH on Linux.


Excellent idea! +1
The only suggestion I have is that would be hesitant to set the configuration per service
constructor. The configuration is typically done globally on a per process basis and there
be an option to do it globally and programmatically.
For example adding a method to Axis.cpp:
static void Axis::setConfig(AxisCPP_Configuration conf);
which sets g_pConfig.
My 2c,
-----Original Message-----
From: John Hawkins []
Sent: Friday, May 06, 2005 6:40 AM
Subject: New client configuration API

Hi Folks, 

we'd like to implement a new API for configuration of the client-side. 

I've written a vrief synopsis of what is there to day and what we'd like to do.......... 

The environment variable is AXISCPP_DEPLOY. This variable is used by the configuration system
to look up a file called axiscpp.conf. This file consists of the following: 

#ClientLogPath:                 The path to the axis client log 
#ClientWSDDFilePath:         The path to the client wsdd 
#XMLParser:                 The xml parser library 
#Transport_http:                 The HTTP transport library 
#Channel_HTTP:                 The HTTP transport channel library 
#Channel_HTTP_SSL:         The HTTP transport secure channel library 

This data can be placed in a new configuration Object with the following signature (Pseudo)

        get/set ClientLog(String); 
        get/set ClientWSDDFile(String); 
get/set XMLParserLibrary(String); 
get/set TransportLibrary(String); 
get/set HTTPChannelLibrary(String); 
get/set HTTPSSLChannelLibrary(String); 

A new Web Service constructor will be created that takes in an AxisCPP_Configuration object.
This constructor will be in addition to the current range of constructors that are created
for each service. 

The user may create a web service using the constructor. However, if they attempt to use the
constructor with a configuration object more than once in any given process the configuration
object will be ignored i.e. the engine can only be configured once per process. 

Client WSDD files will still be required and no new API will be introduced for them. 

thoughts please? 


> Programmatic configuration
> --------------------------
>          Key: AXISCPP-426
>          URL:
>      Project: Axis-C++
>         Type: New Feature
>   Components: Configuration
>     Versions: future (enh)
>  Environment: all
>     Reporter: Tim Bartley

> It would be useful to be able to provide all configuration information programatically
not least to prevent interaction between different clients and servers.
> Regards,
> Tim

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message