Hi Subash, I believe that you are quoting a POC that we did originally. But, in the context of a generic C-App governance implementation,
1. I wouldn't tie a C-App to a project. This is because a single project could produce more than one C-App. What do you call this in Developer Studio? 2. I would move the C-App inside the application folder structure, making it possible for the C-App to change/evolve along with the application. 3. We also have some interest in tying up Application in API Store with C-Apps, which we probably need to sort out as well (but as a part of the G-Reg and API Store alignment stuff). Thanks, Senaka. On Sat, May 12, 2012 at 5:08 PM, Subash Chaturanga <[email protected]> wrote: > Hi all, > Following is the screen shot of the $subject. In fact this is the front > end view. > > Here, please note the newly added 3 governance artifacts. > - Applications > - Servers > - Environments > > In brief, > - We can add servers by giving a carbon server endpoint with credentials > along with a suitable name. > - And environments can be created and attach multiple servers (which were > already created) to it. > - Then we can create our project with multiple such environments. And > there we should give a car file location from the repository(currently). > > And the car will get deployed in the given carbon server when the project > created. > > Hi Senaka, > Following will be some points to be considered if greg gonna ship with > this functionality. > > - As per your suggestion, already renamed "Projecst" RXT to "Applications" > and the location of the car file storage. > > * The car file is currently added through a remote client. But we can make > it done through the application RXT. > * And the car files currently gets stored inside > /_system/governance/carbonapps. And when the Application evolves through a > LC, the car file not get migrated. > But stored in a separate place as mentioned above. If the car file not > gonna change, it is seems OK to not to migrate it to branches with LC state > and keep it separate. > And as it is not likely to happen, I also don't think that's a good idea > to keep it separate. Shall we put it > inside......../applications/myapplication_1/ > > Any ideas ? > > Please add any missing/required facts needs to be considered. > > > > Thanks > -- > > Subash Chaturanga > Software Engineer > WSO2 Inc. http://wso2.com > > email - [email protected] > phone - 077 2225922 > > -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
