Hi Deepal, On Sun, Feb 21, 2010 at 8:16 PM, Deepal jayasinghe <deep...@gmail.com>wrote:
> > > > > Regarding the INFO message that gets logged per service, at > > deployment. The better side of this is that you get a confirmation to > > whether your service got deployed. But, the bad side of it is that, if > > there are 1000+ services hosted (for example), we'll be printing 1000s > > of such messages. > Practically speaking it is not good idea to put 1000+ services in one > Web service server and it is extremely hard to manage. That is why we > have something called service compositions and ESBs. > I just took a nasty example.. :-)... > > Also, once a person is certain that a particular service is deployed > > successfully, a confirmation would not be required per each server > > reboot, unless he did some change. > I think this is wrong assumption, working a service one time does not > mean it is going to work forever. So it is required to validate service > deployment after each system reboot. > This is something questionable. If a service got deployed once successfully, can it fail at the next reboot? "without" any changes being done? If so, the deployment is not predictable. I'm excluding the possibility of a service failing to deploy due to some issues in its implementation, which can change per each deployment made, which could cause such issues. This is because, managing such error situations should be a responsibility of the service author. Thanks, Senaka. > > So, it would be great if this could be made something optional (a > > development time thing), where the default will be not to print > > anything unless something goes wrong in the deployment process (which > > will print an error or warning, as it suits). This is IMHO. > > > For me change you guys have done is very simple, it does not affect > anything, no performance overhead. > > WDYT? > > > > Thanks, > > Senaka. > > > > On Sun, Feb 21, 2010 at 7:50 PM, Glen Daniels <g...@thoughtcraft.com > > <mailto:g...@thoughtcraft.com>> wrote: > > > > Hi Ruwan, all, > > > > I'm afraid I don't get this change. Amila makes a good point I > > think; I can > > totally understand why you wouldn't want certain services showing > > up on the > > UI (although even then you would want admins to see them), but the > > INFO > > message is on the actual console of the server, which only admins > > should have > > access to anyway. What do you gain from this change, aside from > > making it > > harder to tell if your services are coming up correctly or not? :) > > > > --Glen > > > > On 2/21/2010 5:18 AM, Amila Suriarachchi wrote: > > > > > > > > > On Sat, Feb 20, 2010 at 8:29 PM, Ruwan Linton > > <ruwan.lin...@gmail.com <mailto:ruwan.lin...@gmail.com> > > > <mailto:ruwan.lin...@gmail.com <mailto:ruwan.lin...@gmail.com>>> > > wrote: > > > > > > Devs, > > > > > > WSO2 Carbon [http://wso2.org/projects/carbon] which depends > > on and > > > uses axis2 has a requirement to have hidden admin services, > > > > > > I think a hidden service is a service which should not display > > in the > > > carbon Admin console. > > > > > > > > > bu the DeploymentEngine prints an INFO log message for all the > > > service deployments, in order to achieve the above requirement, > > > > > > What is the problem with this INFO message print in the command > > line or > > > a log file? I think those INFO messages are only visible to > > admin or who > > > ever access to deployments. Isn't it nice to know even these Admin > > > services get deployed properly? > > > > > > Thanks, > > > Amila. > > > > > > how about filtering this log statement by looking at a > > service group > > > parameter named hiddenService. > > > > > > If there is no objection I will get this implemented. > > > > > > Thanks, > > > Ruwan > > > > > > -- > > > Ruwan Linton > > > Technical Lead & Product Manager; WSO2 ESB; > http://wso2.org/esb > > > WSO2 Inc.; http://wso2.org > > > email: ru...@wso2.com <mailto:ru...@wso2.com> > > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>; cell: +94 77 341 > 3097 > > > blog: http://ruwansblog.blogspot.com > > > > > > > > > > > > > > > -- > > > Amila Suriarachchi > > > WSO2 Inc. > > > blog: http://amilachinthaka.blogspot.com/ > > > > > > > > > > -- > > Senaka Fernando > > Software Engineer > > WSO2 Inc. > > E-mail: senaka AT wso2.com <http://wso2.com>; Mobile: +94 77 322 1818 > > > > http://www.wso2.com/ - "Lean . Enterprise . Middleware" > > > -- > Thank you! > > > http://blogs.deepal.org > http://deepal.org > > -- Senaka Fernando Software Engineer WSO2 Inc. E-mail: senaka AT wso2.com; Mobile: +94 77 322 1818 http://www.wso2.com/ - "Lean . Enterprise . Middleware"
