On Fri, Apr 25, 2014 at 4:44 AM, Chintana Wilamuna <[email protected]>wrote:
> First of all I think the subject of the mail is a bit misleading or my > understanding of Jaggery is incomplete. Jaggery, to me should always be > like PHP or NodeJS. There shouldn't be any impose from the platform for > rigid config locations. This comes from the Java app server mindset. > > Application developer should have the freedom to have any config file in > any format anywhere. Is it not? > AFAIK there is a GSoC project going on to support Jaggery on Tomcat ( technically any Servlet container) in such context there is no registry. IMHO best approach is let developers to decide where to keep configuration files etc, may be you can include a sample to demonstrate how to use registry to store Jaggery configurations. Thanks ! > > -Chintana > > > On Fri, Apr 18, 2014 at 10:37 AM, Manuranga Perera <[email protected]> wrote: > >> *Current Implementation* >> We currently keep configuration files for jaggery apps within the app >> itself (eg: site.json). >> >> *Issue with Current Implementation* >> But this is creating some difficulties in multi environment deployments. >> Since the configuration files will contain some environment specific >> information (eg: SSO IDP URL), this makes the artifacts un-portable across >> environments. >> >> *Suggested Solution* >> We can implement a mechanism where the configuration is read from an >> outside location (eg: repository/conf) at deployment time and keep it in >> the application context and reuse it. >> >> >> Let's discuss the feasibility of this solution. alternative solutions are >> welcome. >> >> -- >> With regards, >> *Manu*ranga Perera. >> >> phone : 071 7 70 20 50 >> mail : [email protected] >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Chintana Wilamuna > Architect - Solutions Architecture > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > phone: +94 72 145 4545 > blog: http://engwar.com/ > photos: http://flickr.com/photos/chintana > linkedin: http://www.linkedin.com/in/engwar > twitter: twitter.com/std_err > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services; http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
