+1 for the changes. Do we have any plans for hot update feature for services. Also good to change deployment engine in a suitable manner to support services written in scripting languages like JavaScript or Python. We must have a mechanism to directly deploy the script files, if we are going to support these features in the future.
Thanks, Milinda On 10/8/07, Chintana Wilamuna <[EMAIL PROTECTED]> wrote: > > On 10/8/07, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote: > > > Damitha Kumarage wrote: > > > I have a question here. If we start two servers of the same > > > transport(say http) are we allowed to use the same axis2.xml > > > configuration file for both servers?. I guess they need different > > > configuration files located in different places. If someone try to > > > load from same conf file he should be warned that a server already > > > stared in the same context and thwart his second attempt. > > Why should we restrict this? I think sometimes it is useful, at least > > for test purposes to start two instance of the same server using the > > same transport and same conf file. > > How about, by default it uses the same config file and a command line > switch to specify a different config file? (e.g. > --use-config=/my/config/file) > > Bye, > > -Chintana > > -- > http://engwar.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://think2ed.blogspot.com "thinksquared" http://wsaxc.blogspot.com "Web Services With Axis2/C"
