Re: [Architecture] Moving deployment section from configuration xml and Facilitate AppFactory users to deploy apps with their custom app types if its not already available

Hi Dimuthu We are staying at one configuration because only changing configuration when stage changes are cartidge type and alias. So we can append the stage to the given value from code when we read it easily. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile

Re: [Architecture] Moving deployment section from configuration xml and Facilitate AppFactory users to deploy apps with their custom app types if its not already available

Hi Dimuthu and All We decided to go with a separate file for this runtime configs. So we will deploy this file to a different location with a different axis2 deployer. And we will mention in the apptype.xml which runtime to be used. WDYT? Thanks Regards Danushka Fernando Software Engineer WSO2

Re: [Architecture] Moving deployment section from configuration xml and Facilitate AppFactory users to deploy apps with their custom app types if its not already available

Hi Rajeevan, Could you explain a bit more on how we are going to relate the lifecycle stage with the runtime? If you look at the appfactory.xml, you might have noticed that the Deployer information is defined for each lifecycle stage. So with this new runtime.xml, how are we going to address

Re: [Architecture] Moving deployment section from configuration xml and Facilitate AppFactory users to deploy apps with their custom app types if its not already available

Hi Guys, Please start with why. Lets do minimal to achieve why with most healthiest way. Why we need to do this is to external parties to add interpreter based languages and their cartridges. We do not need a new deployer type right now. I proposed a new Runtime object only because we need to

Re: [Architecture] Moving deployment section from configuration xml and Facilitate AppFactory users to deploy apps with their custom app types if its not already available

Hi, If you have a deployer and it it is working keep it. But please don't add anymore features to this. We need to operate on why principle. Janaka if we go ahead with what you are saying it is a new feature. Current architecture is flexible and would make us think of many possibilities, but lets

Re: [Architecture] Moving deployment section from configuration xml and Facilitate AppFactory users to deploy apps with their custom app types if its not already available

Hi Dimuthu, On Thu, Dec 4, 2014 at 10:42 AM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi Guys, Please start with why. Lets do minimal to achieve why with most healthiest way. Why we need to do this is to external parties to add interpreter based languages and their cartridges. We do not

Re: [Architecture] Moving deployment section from configuration xml and Facilitate AppFactory users to deploy apps with their custom app types if its not already available

Hi Janaka, Understood the question. :) +1. We need 3 runtimes defined - one per each lifecycle. thanks, dimuthu On Thu, Dec 4, 2014 at 11:14 AM, Janaka Ranabahu jan...@wso2.com wrote: Hi Dimuthu, On Thu, Dec 4, 2014 at 10:42 AM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi Guys,

Re: [Architecture] Moving deployment section from configuration xml and Facilitate AppFactory users to deploy apps with their custom app types if its not already available

Hi Dimuthu/All, In addition to this mail conversation we had discussed this in an internal forum, Here is the update of thatdiscussion As of today We are using appfactory.xml file for the runtime configurations the below fraction is the the configuration properties. ApplicationType name=*

Re: [Architecture] Moving deployment section from configuration xml and Facilitate AppFactory users to deploy apps with their custom app types if its not already available

HI Rajeevan, No GUI please. We are changing the whole user story here. thanks, dimuthu On Wed, Dec 3, 2014 at 10:54 AM, Aiyadurai Rajeevan rajeev...@wso2.com wrote: Hi Dimuthu/All, In addition to this mail conversation we had discussed this in an internal forum, Here is the update of

Re: [Architecture] Moving deployment section from configuration xml and Facilitate AppFactory users to deploy apps with their custom app types if its not already available

Hi Dimuthu, Thanks for the suggestion. So, As a conclusion I will go ahead with the implementation as having a runtime.xml for the whole below peroperties and populate a map from there. Runtime Runtimeappserver/Runtime

[Architecture] Moving deployment section from configuration xml and Facilitate AppFactory users to deploy apps with their custom app types if its not already available

Hi All, We are trying to implement a feature on AF which enables the user to deploy their customized app types, Currently this configuration is available in *appfactory.xml *under *Deployer* tag the content would be as [1], likewise we have for each app types. Hence this wouldn't be editable by

Re: [Architecture] Moving deployment section from configuration xml and Facilitate AppFactory users to deploy apps with their custom app types if its not already available

Hi Rajeevan, Please see my comments below. On Mon, Dec 1, 2014 at 10:46 PM, Aiyadurai Rajeevan rajeev...@wso2.com wrote: Hi All, We are trying to implement a feature on AF which enables the user to deploy their customized app types, Currently this configuration is available in

Re: [Architecture] Moving deployment section from configuration xml and Facilitate AppFactory users to deploy apps with their custom app types if its not already available

Hi, On a side note, I would call it s/Deployment/Runtime. I think it is a more suitable name. thanks, dimuthu On Tue, Dec 2, 2014 at 8:45 AM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi Rajeevan, Please see my comments below. On Mon, Dec 1, 2014 at 10:46 PM, Aiyadurai Rajeevan

Re: [Architecture] Moving deployment section from configuration xml and Facilitate AppFactory users to deploy apps with their custom app types if its not already available

Hi, +1 with the proposals. I couldn't find the appfactory-plugin.xml, though. Did you mean to say the jelly files(conf.jelly and global.jelly) which is inside the AppfactoryPluginManager? Thanks Regards, S.A.Rajeevan Software Engineer WSO2 Inc E-Mail: rajeev...@wso2.com | Mobile : +94776411636

Re: [Architecture] Moving deployment section from configuration xml and Facilitate AppFactory users to deploy apps with their custom app types if its not already available

Hi, We used to have a *plugin*.xml file. I can't find it anymore. Perhaps it is time to re-introduce it. thanks, dimuthu On Tue, Dec 2, 2014 at 10:31 AM, Aiyadurai Rajeevan rajeev...@wso2.com wrote: Hi, +1 with the proposals. I couldn't find the appfactory-plugin.xml, though. Did you mean

Re: [Architecture] Moving deployment section from configuration xml and Facilitate AppFactory users to deploy apps with their custom app types if its not already available

HI Dimuthu Please find my comments inline On Tue, Dec 2, 2014 at 8:45 AM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi Rajeevan, Please see my comments below. On Mon, Dec 1, 2014 at 10:46 PM, Aiyadurai Rajeevan rajeev...@wso2.com wrote: Hi All, We are trying to implement a feature

Re: [Architecture] Moving deployment section from configuration xml and Facilitate AppFactory users to deploy apps with their custom app types if its not already available

Hi Danushka, Please see my comments below. On Tue, Dec 2, 2014 at 12:01 PM, Danushka Fernando danush...@wso2.com wrote: HI Dimuthu Please find my comments inline On Tue, Dec 2, 2014 at 8:45 AM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi Rajeevan, Please see my comments below.