Sanjaya Karunasena wrote:
I am bit confused here. Why do we couple http transport with logging. I
see a violation of seperation of concerns. This logging is for Axis2.
Http is just one of the transports. Resposibility shoud be with Axis2.
This is about accepting the configuration parameters as server startup
arguments.
For example maximum log file size is given for simple axis2 server
./axis2_http_server -LOG_FILE_SIZE <value in mb>
Similarly we need a way to provide this when starting apache2 server
with axis2 module plugged in. This argument value is appropriatly
handled by our server startup code and pass to the logging module which
has no dependancy on transport :)
So my question is shouldn't that be part of axis2.xml? httpd.conf belongs
to the http server. If I run this only using TCP?
What if I run two server instances using the same axis2.xml?
Is it two server instances or supporting two transports?
Can be both.
I can run simple axis server as well as httpd with the same repo (same
services and modules)
I can also use http with simple axis server and tcp with tcp server with
the same repo as well.
Samisa...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
