On Fri, May 10, 2013 at 5:39 AM, Pradeep Fernando <prad...@wso2.com> wrote:
> Hi, > > Some of the 3 rd party jars search config files from their classPath. > However due to one loader per bundle policy of OSGi, the class path is > fragmented. There are two options to solve this issue, > > - use absolute paths > - use fragment bundles > > the latter option, > > say if the bundle foo needs config file bar.xml. How about user creates a > directory named 'foo' under conf directory and put the config file there. > During the startup, we create new fragment bundle out of bar.xml and attach > it to bundle foo. > Why user need to put that file to foo folder? I think the bar.xml file is inside the third party jar. So I think carbon should take all such files can create the fragment host. thanks, Amila. > > we are doing similar thing in log4j.properties file. but the approach is > not generic at the moment. WDYT ? > > --Pradeep > > > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
