Hi, Thanks for the response. Will work work accordingly.
Thanks, Manoj Best Regards.. Manoj Kumara Software Engineer WSO2, Inc.; http://wso2.com Twitter: http://twitter.com/ManKuma Mobile: +94713448188 On Sat, Aug 17, 2013 at 8:55 PM, Sagara Gunathunga <[email protected]> wrote: > > > > On Sat, Aug 17, 2013 at 7:18 PM, Manoj Kumara <[email protected]> wrote: > >> Hi, >> >> I'm currently looking at the issue [1] reported on $subject. It will be >> great if you can advice me on what would be the expected behavior in such a >> scenario if the current approach is not correct. >> > > Since we support hot-update for both services and web applications > expected behavior should be when the new deployment artifact available old > one should be undeployed and newer one get deployed with same > service/context name. > > Thanks ! > >> >> [1] https://wso2.org/jira/browse/WSAS-1439 >> >> >> Thanks, >> Best Regards.. >> >> >> Manoj Kumara >> Software Engineer >> WSO2, Inc.; http://wso2.com >> >> Twitter: http://twitter.com/ManKuma >> Mobile: +94713448188 >> > > > > -- > Sagara Gunathunga > > Senior Technical Lead; WSO2, Inc.; http://wso2.com > V.P Apache Web Services; http://ws.apache.org/ > Linkedin; http://www.linkedin.com/in/ssagara > Blog ; http://ssagara.blogspot.com > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
