axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lilantha Darshana <>
Subject RE: [AXIS-C++] AxisEngine should not be a singleton & it needs re fact oring.
Date Wed, 23 Jul 2003 06:20:09 GMT
AxisEngine should be able to be configured depending on user requirements,
and properties of deployed services, handlers etc.. For an example 
engine should be configured depending on what you have in
"server-config.wsdd" or you can create your own Server Config (like
& and hard code the TransportHandlers & chains etc. 
(Glen - correct me if I'm wrong). OR  when you want to programmatically 
deploy components like Handlers, Transports, and Services which is 
handy when you want to start with a base configuration or the
default WSDD and then dynamically add stuff without changing 
the WSDD document.

These configuration could be depends on the sessions as well! 
So having a singleton will restrict that.


-----Original Message-----
From: []
Sent: Wednesday, July 23, 2003 11:19 AM
Subject: Re: [AXIS-C++] AxisEngine should not be a singleton & it needs
refact oring.

What would be engine configuration properties. can you give an example?

On Mon, 21 Jul 2003 08:32:05 -0400, Lilantha Darshana wrote
> Hi C++ team,
> I guess AxisEngine SHOULD NOT be a class-wide global singleton 
> object. Engine configuration should be done for each user sessions. 
> So singleton objects restricts this requirement. Please make it not 
> to be a singleton.
> It would be better if AxisClient & AxisServer can be derived from the
> AxisEngine and
> AxisEngine share common functionalities for both. Please refactor
> & derive
> AxisServer (for now -- and later AxisClient) from AxisEngine so that 
> future extensions are easy.
> regards
> Lilantha

University of Colombo Web-mail Service (

View raw message