On Sat, Feb 20, 2010 at 8:44 PM, Deepal jayasinghe <deep...@gmail.com>wrote:
> Ruwan Linton wrote: > > No those are normal services, > You are contradicting yourself. > Nope, I am not. Administrator services can exists as aar services, jar service and osgi bundle based services. > acting as admin services, to provide the server administration > > framework. This cannot be solve with a deployer. > of course you can, sometimes administrator services needs additional > paramters than normal service, for example if you do not want to display > them under list services, then you can customize them using the custom > deployer. > AFAIK, in-order to do this, we need to at least put these services into a different directory or has to have a different extension, please see my above comment. They are normal aar, jar services which provides some server administration operations. > > Also I don't see this as a hack. > Either way I have no problem, but I see long term advantage of having > separate deployer for admin service, I bet you that you will soon have > some other additional requirements. > Hhhmm, for now it is just this... and I don't see any near future requirements, so I would add this param check before the INFO log, which will have no harm at all. Thanks, Ruwan > > > > Thanks, > > Ruwan > > > > On Sat, Feb 20, 2010 at 8:32 PM, Deepal jayasinghe <deep...@gmail.com > > <mailto:deep...@gmail.com>> wrote: > > > > How about adding a hidden service deployer ? I think that approach is > > much cleaner than hacking the code. > > > Devs, > > > > > > WSO2 Carbon [http://wso2.org/projects/carbon] which depends on and > > > uses axis2 has a requirement to have hidden admin services, bu the > > > DeploymentEngine prints an INFO log message for all the service > > > deployments, in order to achieve the above requirement, 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 > > > > > > -- > > Thank you! > > > > > > http://blogs.deepal.org > > http://deepal.org > > > > > > > > > > -- > > 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>; cell: +94 77 341 3097 > > blog: http://ruwansblog.blogspot.com > > > -- > Thank you! > > > http://blogs.deepal.org > http://deepal.org > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://ruwansblog.blogspot.com
