Hi all, When looking into the CEP 3.1.0 osgi services, we (Myself and Manoj) found out that the following registry services were unsatisfied. We found out that the above services were unsatisfied for some released packs as well.
81 Unsatisfied org.wso2.carbon.governance.api org.wso2.carbon.governance.api(bid=275) 110 Unsatisfied org.wso2.carbon.registry.indexing org.wso2.carbon.registry.indexing(bid=358) 116 Unsatisfied registry.search.dscomponent org.wso2.carbon.registry.search(bid=371) It seems this occurs due to indexing config not being available in registry.xml. If this is not available, an NPE is thrown in org.wso2.carbon.registry.indexing.RegistryConfigLoader constructor which is run when registering the registry service for the org.wso2.carbon.registry.indexing bundle. Therefore this NPE is not logged anywhere and those registry.indexing service fails to register. As a workaround for this issue, you can to add an *<indexingConfiguration>*element to registry.xml. But I think the correct fix is to catch the exception in *org.wso2.carbon.registry.indexing.RegistryConfigLoader* constructor and assign defaults as has been done for other parameters of the class. Thanks, Lasantha -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: [email protected] mobile: (+94) 71 5247551
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
