Hi
    I think the approach  (according to my understanding) should  be
something similar to* log4j.properties* bundling
 (Log4jPropFileFragmentBundleCreator.java) where the bundle creation
process is defined *org.wso2.carbon.server *and during the run time it
creates a fragment bundle jar and place it to the dropins  *
(org.wso2.carbon.logging.propfile_1.0.0.jar)* , so probably we may have to
write a* new extension* (*may be in the platform level*) to extract *synapse
driven external configuration* and bundle them and place them to the
dropins where it will be visible to the class path then

cheers
Dushan

On Tue, May 22, 2012 at 1:41 PM, Hiranya Jayathilaka <hira...@wso2.com>wrote:

> So Synapse looks for the config files in appClassPath. How do we include a
> config file in appClassPath with the current model?
>
> On Tue, May 22, 2012 at 10:55 AM, Pradeep Fernando <prad...@wso2.com>wrote:
>
>> Hi,
>>
>> Any properly written library allow their users to feed-in config files
>> using,
>>
>> 1. jre classPath
>> 2. appClassPath
>> 3. reside within the same jar - similar to appclasspath
>> 4. system property
>>
>> This is the standard search order of a config file. The whole point of
>> OSGi module layer is to have independent classPaths. So basically, if
>> we are going to support a common place for all the config files, we
>> have to introduce a new classsLoader as the parent classLoader of
>> bunldeClassLoader.
>>
>> Normally the parent being, boot or ext. I don't think it is
>> technically possible (not sure 100%). Even if it is possible we should
>> not do such hacks.
>>
>> thanks,
>> --Pradeep
>>
>
>
>
> --
> Hiranya Jayathilaka
> Senior Technical Lead;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>



-- 
Dushan Abeyruwan
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/*
*Mobile:(+94)714408632*
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to