+1 for using touchpoints. Thanks, Senaka.
On Fri, Apr 4, 2014 at 9:49 PM, Lasantha Fernando <[email protected]> wrote: > Hi Ajith, > > Can we add a null check to the constructor code or log the error and > throw? > > The actual cause is indeed the missing configs, but it is hard to debug > because that NPE simply causes the bundle instance to not be created, and > dependent bundles also become unsatisfied. > > > On 4 April 2014 21:06, Ajith Vitharana <[email protected]> wrote: > >> Hi Manoj/Lasantha, >> >> I just checked the fresh G-Reg pack without indexing config in >> registry.xml and it is working fine without any issue. >> When you install some registry feature to others products, you should add >> the related configs (handler config ..etc ) to work that features properly. >> >> AFAIK, there is no way to add config sections to existing configuration >> files while installing features. >> > > Maybe can we use the new touchpoints introduced in Carbon 4.2.0 [1] for > this? > > [1] > https://docs.wso2.org/display/Carbon420/Adding+and+Removing+XML+Element+Touchpoint+Actions > > Thanks, > Lasantha > > >> Thanks. >> Ajith. >> >> >> >> On Fri, Apr 4, 2014 at 4:54 PM, Manoj Kumara <[email protected]> wrote: >> >>> [Adding Greg Team] >>> >>> Can Greg team please have a look on this. >>> >>> Thanks, >>> Manoj >>> >>> >>> *Manoj Kumara* >>> Software Engineer >>> WSO2 Inc. http://wso2.com/ >>> *lean.enterprise.middleware* >>> Mobile: +94713448188 >>> >>> >>> On Fri, Apr 4, 2014 at 4:49 PM, Lasantha Fernando <[email protected]>wrote: >>> >>>> 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 >>>> >>> >>> >> >> >> -- >> Ajith Vitharana. >> WSO2 Inc. - http://wso2.org >> Email : [email protected] >> Mobile : +94772217350 >> >> > > > -- > *Lasantha Fernando* > Software Engineer - Data Technologies Team > WSO2 Inc. http://wso2.com > > email: [email protected] > mobile: (+94) 71 5247551 > -- *[image: http://wso2.com] <http://wso2.com> Senaka Fernando* Senior Technical Lead; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
