Glenn Williams wrote:
Axis2.xml, from the documentation, is supposed to be for global
configuration. But it is available outside .AAR file so a user could change
the configuration without repackaging the .AAR file. But that seems to
violate the usage of the axis2.xml file. Any thoughts?
What do you think about putting a configuration file for the given service
in the Axis2 conf directory? Is that directory available to the service at
runtime?
IFAIK, you only get access to ConfigurationContext which reflects configuration
specified in axis2.xml in runtime. You can't access the contents of axis2 conf
directory directly.
IMHO, configuration file of a service should be included in service.aar file.
I would put it inside META-INF folder inside service.aar and later read it
via service class loader.
Thanks,
Sanka
-----Original Message-----
From: Deepal jayasinghe [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 06, 2007 4:54 AM
To: axis-user@ws.apache.org
Subject: Re: Runtime best practices for Axis2
Glenn Williams wrote:
What are the best practices for passing runtime parameters (such as DB
login, pooling parameters) to the Axis2 container?
You can add them as parameters in axis2.xml or you can have a module to
initialize them and add those to container. In the case of module
approach you have to write a module with a Module class and inside the
module init method you need to do the processing.
Thanks
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Sanka Samaranayake
WSO2 Inc.
http://www.bloglines.com/blog/sanka
http://www.wso2.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
