Hi, In our current implementation to deploy a new service the server needs to be restart. But in a production enviournment it is very efficient if we support picking services without restarting the server. So if we are going to support such a scenario in the future won't the proposed solution be a problem? Because to add a new service the user need to edit the conf file. But with the current repo structure adding such a feature is far more easy.
Apart from the above issue I am +1 for the changing the repository structure. -Manjula. On Mon, 2007-10-08 at 13:20 +0600, 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... > > Samisa... > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
