Hi I think we have come to a solution like setting up the external config location as system property and load respective property files from their, and we have agreed to* reject the fragment bundle property file loading mechanism since its a close to kind of a hack and not the best practice among to load properties*, currently the config location is specified at wso2server(.sh/bat) as -Dconf.location="$CARBON_HOME/repository/conf"\ ,/ -Dconf.location ="%CARBON_HOME% \repository\conf" thus respective components first looking in to the system property define path if not followed by its classloader context , any other ideas? ,
cheers Dushan On Thu, Jun 21, 2012 at 9:21 AM, Afkham Azeez <[email protected]> wrote: > Have we found a proper solution to this issue? I'm sure users will have > custom libraries that they use which will require loading of properties > files from the classpath. So we need to sort this out, if it has not > already been sorted out. > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **[email protected]* <[email protected]>* cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > * > * > *Lean . Enterprise . Middleware* > > -- Dushan Abeyruwan *Senior Software Engineer* *Integration Technologies Team* *WSO2 Inc. http://wso2.com/* *Mobile:(+94)714408632*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
