Re: [Dev] Configuration location for jaggery apps
On Fri, Apr 25, 2014 at 12:16 PM, Manuranga Perera m...@wso2.com wrote: Hi Chintana, Sagara, you are correct about the user written apps. this discussion is about jaggery apps we ship by default with wso2 products. Technically are there any differences among Jaggery apps developed by WSO2 and NON-WSO2 ? Let me take an example from AS, in AS you can create a Java web application and possible to keep some configurations on Registry ( e.g - Carbon Admin Console) while someone can completely ignore the present of Registry and write apps I think this is same for Jaggery apps as well. Thanks ! On Thu, Apr 24, 2014 at 4:14 PM, Chintana Wilamuna chint...@wso2.comwrote: 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? -Chintana On Fri, Apr 18, 2014 at 10:37 AM, Manuranga Perera m...@wso2.com 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 : m...@wso2.com ___ Dev mailing list Dev@wso2.org 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 -- With regards, *Manu*ranga Perera. phone : 071 7 70 20 50 mail : m...@wso2.com ___ Dev mailing list Dev@wso2.org 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 Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Configuration location for jaggery apps
Hi Manu, What do we are going to keep in repository/conf? Is it all configurations for that app or just the env dependent configs? My point is, if apps have env independent configs, where do we keep them. If we keep them too in repository/conf, then that would not be scalable. So, are we going with two locations for configs or ?? How about loading configs from each app by looking at the repository/conf directory? i.e. They can override the config from repository/conf directory. If it has one, then that will be picked, else what can be seen within the app will be picked. But, not sure how would be the experience when we have the same config in two places. /Ruchira On Fri, Apr 25, 2014 at 12:16 PM, Manuranga Perera m...@wso2.com wrote: Hi Chintana, Sagara, you are correct about the user written apps. this discussion is about jaggery apps we ship by default with wso2 products. On Thu, Apr 24, 2014 at 4:14 PM, Chintana Wilamuna chint...@wso2.comwrote: 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? -Chintana On Fri, Apr 18, 2014 at 10:37 AM, Manuranga Perera m...@wso2.com 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 : m...@wso2.com ___ Dev mailing list Dev@wso2.org 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 -- With regards, *Manu*ranga Perera. phone : 071 7 70 20 50 mail : m...@wso2.com -- *Ruchira Wageesha**Associate Technical Lead* *WSO2 Inc. - lean . enterprise . middleware | wso2.com http://wso2.com* *email: ruch...@wso2.com ruch...@wso2.com, blog: ruchirawageesha.blogspot.com http://ruchirawageesha.blogspot.com, mobile: +94 77 5493444* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Configuration location for jaggery apps
Hi Chintana, Sagara, you are correct about the user written apps. this discussion is about jaggery apps we ship by default with wso2 products. On Thu, Apr 24, 2014 at 4:14 PM, Chintana Wilamuna chint...@wso2.comwrote: 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? -Chintana On Fri, Apr 18, 2014 at 10:37 AM, Manuranga Perera m...@wso2.com 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 : m...@wso2.com ___ Dev mailing list Dev@wso2.org 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 -- With regards, *Manu*ranga Perera. phone : 071 7 70 20 50 mail : m...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Configuration location for jaggery apps
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? -Chintana On Fri, Apr 18, 2014 at 10:37 AM, Manuranga Perera m...@wso2.com 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 : m...@wso2.com ___ Dev mailing list Dev@wso2.org 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 Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Configuration location for jaggery apps
On Fri, Apr 25, 2014 at 4:44 AM, Chintana Wilamuna chint...@wso2.comwrote: 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 m...@wso2.com 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 : m...@wso2.com ___ Dev mailing list Dev@wso2.org 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 Dev@wso2.org 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 Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Configuration location for jaggery apps
Or cant we create the configurations based on the environment at the startup maybe ? I assume you need to change the hostname/port etc right ? I am trying do do this, but direct references to site.json are in lot of places (I am looking at APIM store). so to avoid doing lot of custom changes, I'll try writing the correct config back to site.json at start-up time. 1. If it is packed with the product, you can simply keep the site.json file as a template in puppet or in a suitable way if you are using any other config management mechanisms. we are tying to avoid situations where things in deployment/server directory are managed directly by puppet. because it creates problems with multi management node setups, when multiple noes try to commit at start-up. -- With regards, *Manu*ranga Perera. phone : 071 7 70 20 50 mail : m...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Configuration location for jaggery apps
On Mon, Apr 21, 2014 at 10:23 PM, Manuranga Perera m...@wso2.com wrote: Or cant we create the configurations based on the environment at the startup maybe ? I assume you need to change the hostname/port etc right ? I am trying do do this, but direct references to site.json are in lot of places (I am looking at APIM store). so to avoid doing lot of custom changes, I'll try writing the correct config back to site.json at start-up time. 1. If it is packed with the product, you can simply keep the site.json file as a template in puppet or in a suitable way if you are using any other config management mechanisms. we are tying to avoid situations where things in deployment/server directory are managed directly by puppet. because it creates problems with multi management node setups, when multiple noes try to commit at start-up. That issue will come if you start all the management nodes at once, isn't it? If you start one by one, I don't think such an issue will be there. Have you tried it? -- With regards, *Manu*ranga Perera. phone : 071 7 70 20 50 mail : m...@wso2.com -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Configuration location for jaggery apps
An alternative solution can be proposed based on the nature of the jaggery app. i.e. is it available in the product itself, similar to publisher and store apps of APIM or is it an app you deploy in to AppServer or any other server. 1. If it is packed with the product, you can simply keep the site.json file as a template in puppet or in a suitable way if you are using any other config management mechanisms. 2. If the app is deployed in to a server, then it is somewhat difficult to manage the config files. Then, one option is to bundle the correct config file at the build time (using some maven params or ant stuff). I don't think we should change the way how the config is read. This could be done with alternatives according to your requirements. But, there is no concrete solution IMO. On Fri, Apr 18, 2014 at 11:07 PM, Manuranga Perera m...@wso2.com 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 : m...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Configuration location for jaggery apps
On Sun, Apr 20, 2014 at 12:48 PM, Amila Maha Arachchi ami...@wso2.comwrote: An alternative solution can be proposed based on the nature of the jaggery app. i.e. is it available in the product itself, similar to publisher and store apps of APIM or is it an app you deploy in to AppServer or any other server. 1. If it is packed with the product, you can simply keep the site.json file as a template in puppet or in a suitable way if you are using any other config management mechanisms. +1 2. If the app is deployed in to a server, then it is somewhat difficult to manage the config files. Then, one option is to bundle the correct config file at the build time (using some maven params or ant stuff). I don't think we should change the way how the config is read. This could be done with alternatives according to your requirements. But, there is no concrete solution IMO. On Fri, Apr 18, 2014 at 11:07 PM, Manuranga Perera m...@wso2.com 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 : m...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Configuration location for jaggery apps
On Sun, Apr 20, 2014 at 7:26 PM, Madhuka Udantha madh...@wso2.com wrote: On Sun, Apr 20, 2014 at 12:48 PM, Amila Maha Arachchi ami...@wso2.comwrote: An alternative solution can be proposed based on the nature of the jaggery app. i.e. is it available in the product itself, similar to publisher and store apps of APIM or is it an app you deploy in to AppServer or any other server. 1. If it is packed with the product, you can simply keep the site.json file as a template in puppet or in a suitable way if you are using any other config management mechanisms. +1 How about keeping the configurations in the registry? I don't know how well puppet plays with config jsons in registry though. 2. If the app is deployed in to a server, then it is somewhat difficult to manage the config files. Then, one option is to bundle the correct config file at the build time (using some maven params or ant stuff). I don't think we should change the way how the config is read. This could be done with alternatives according to your requirements. But, there is no concrete solution IMO. On Fri, Apr 18, 2014 at 11:07 PM, Manuranga Perera m...@wso2.com 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 : m...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Configuration location for jaggery apps
On Sun, Apr 20, 2014 at 11:35 PM, Chan duli...@wso2.com wrote: On Sun, Apr 20, 2014 at 7:26 PM, Madhuka Udantha madh...@wso2.com wrote: On Sun, Apr 20, 2014 at 12:48 PM, Amila Maha Arachchi ami...@wso2.comwrote: An alternative solution can be proposed based on the nature of the jaggery app. i.e. is it available in the product itself, similar to publisher and store apps of APIM or is it an app you deploy in to AppServer or any other server. 1. If it is packed with the product, you can simply keep the site.json file as a template in puppet or in a suitable way if you are using any other config management mechanisms. +1 How about keeping the configurations in the registry? I don't know how well puppet plays with config jsons in registry though. Puppet cannot deal with registry stuff. But could be done with some amount of work (may be using registry check-in check-out client). IMO, it is an unnecessary thing. 2. If the app is deployed in to a server, then it is somewhat difficult to manage the config files. Then, one option is to bundle the correct config file at the build time (using some maven params or ant stuff). I don't think we should change the way how the config is read. This could be done with alternatives according to your requirements. But, there is no concrete solution IMO. On Fri, Apr 18, 2014 at 11:07 PM, Manuranga Perera m...@wso2.comwrote: *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 : m...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Configuration location for jaggery apps
On Fri, Apr 18, 2014 at 1:37 PM, Manuranga Perera m...@wso2.com 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. Or cant we create the configurations based on the environment at the startup maybe ? I assume you need to change the hostname/port etc right ? Regards, /Nuwan Let's discuss the feasibility of this solution. alternative solutions are welcome. -- With regards, *Manu*ranga Perera. phone : 071 7 70 20 50 mail : m...@wso2.com -- *Thanks Regards,* * Nuwan Bandara | Senior Technical Lead - Solutions Architecture, WSO2 Inc.+1 812.606.7390 | +1 650.745.4499 Ext 4210 | http://nuwanbando.com http://nuwanbando.com * http://www.nuwanbando.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Configuration location for jaggery apps
*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 : m...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
