If these are not admin services, these should be at least hidden services. Otherwise these should be visible in the services list. So you have to skip admin services and hidden services.
Thanks, ~Isuru On Tue, Mar 20, 2012 at 8:09 AM, Kasun Gajasinghe <kas...@wso2.com> wrote: > Hi, > > I've been working on persistence of globally engaging modules. When > working on this, I noticed that there are services that are Not Admin > Services, but Not user-deployed services (ie. can not be found at > repository/deployment/server) either [1]. We don't engage modules for Admin > services via UI. But the current implementation engage modules to these > non-admin & non-user-deployed services when set a module is globally > engaged. I don't keep persistence files for these services, so this has > become troublesome on what's the use of this, and whether it's possible to > make them Admin Services! > > And, is it needed to set policies for these services [1]? If not, is there > a flag to identify these from user-deployed services? Any help is > appreciated on how to proceed. > > [1] > *org.wso2.carbon.deployment.synchronizer* > org.wso2.carbon.email.verification > org.wso2.carbon.mashup.javascript-scraper > org.wso2.carbon.policyeditor > org.wso2.carbon.email.verification > org.wso2.carbon.mashup.javascript-scraper > org.wso2.carbon.policyeditor > > Thanks, > --KasunG > * > > Kasun Gajasinghe* > Software Engineer; WSO2 Inc.; http://wso2.com > > , > *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813* > *linked-in: *http://lk.linkedin.com/in/gajasinghe* > * > *blog: **http://blog.kasunbg.org* <http://blog.kasunbg.org> > > * > twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> > > * > * > > -- Isuru Suriarachchi Technical Lead WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
