Deepal jayasinghe wrote:
Kaushalye Kapuruge wrote:
Samisa Abeysinghe wrote:
Hi All,
At the moment, we place all our stuff in the repo. Given the repo
location, one can find the axis2.xml, services and modules folders etc.
However, I think that this is quite limiting and inflexible at
times. Say you want to have two different deployments with different
configurations, but with the same services; or you want the same
modules but with different services, so you want to deploy different
servers. At the moment, if you have such a requirement, what you have
to do it to copy the repo to some other location and use it.
If we abstract out the concept of repo and include the service and
module locations in the axis2.xml file itself, then it would be much
more flexible. Then instead of depending a particular folder
structure to find services and modules, we can use the axis2.xml
entries. This way the configuration becomes much more flexible.
Thoughts please...
+1. With a small suggestion.
We can allow users to specify an optional attribute for the module
location.
Like this...
<module ref="module_name" location="/path/to/module">
Hmm , this breaks the similarity between Java and C implementations :)
I assume you are replying to the overall plan. Not just the module
location suggestion.
Yes... It can be. But breaking similarity for an improvement is not a
crime right? :)
Hmm... may be we can achieve the similarity and improvement at the same
time again with a small change in Axis2/Java... ;-)
-Kau
Thanks
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
http://kaushalye.blogspot.com/
http://wso2.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
