Re: [Architecture] RXT Inheritance model for G-Reg 5.0.0

Hi Dimuthu, I too have a small concern about this approach. Before we had the Generic API, we had an API for SOA assets such as Services, WSDL, Schema and Policy. This API was based on a common core but designed for the specific needs of these artifacts. However, this wasn't very useful since

Re: [Architecture] RXT Inheritance model for G-Reg 5.0.0

Hi Subash, Thanks for the quick implementation. It looks enough from App Factory end to achieve what we want. This will allow us to start right away with unified governance model for applications. We'll contribute the Application aspect to the platform. We'll be defining media types for the

Re: [Architecture] RXT Inheritance model for G-Reg 5.0.0

Hi Subash, Awesome! BTW, I still like to know how this parentKey thing works. I thought that it wasn't required to have a parentKey, because it was deducible from the mediatype of the child. Checked your patch, but that's a binary and not the diff, :(. Hi Dimuthu, I didn't quite understand what

Re: [Architecture] RXT Inheritance model for G-Reg 5.0.0

Hi Senaka, On Wed, Aug 6, 2014 at 5:01 PM, Senaka Fernando sen...@wso2.com wrote: Hi Subash, Awesome! BTW, I still like to know how this parentKey thing works. I thought that it wasn't required to have a parentKey, because it was deducible from the mediatype of the child. Checked your

Re: [Architecture] RXT Inheritance model for G-Reg 5.0.0

Hi Subash, Yes, I think so. I think this is implicitly enforced. So, the parent-child model can't be setup between arbitrary mediatypes. Because if we start doing that, people can go crazy with it. Thanks, Senaka. On Wed, Aug 6, 2014 at 12:57 PM, Subash Chaturanga sub...@wso2.com wrote: Hi

Re: [Architecture] RXT Inheritance model for G-Reg 5.0.0

Hi, From AF side we have to provide an API to manage Applications to the platform. This means rather than each and every product using GenericArtifactManager to look for applications they will use a ApplicationArtifactNavigator (which uses GenericaArtifactManager underneath) to CRUD applications.

Re: [Architecture] RXT Inheritance model for G-Reg 5.0.0

Hi Dimuthu, IMHO, the single API for carbon platform to access the unified metadata should be the governance API we provide. If it not meets the platform wide requirement, we have to fix that. What are the things forced AF on using a wrapper governance API. @Sumedha does AM also uses something as

Re: [Architecture] RXT Inheritance model for G-Reg 5.0.0

Hi Subash, That was the conclusion of the discussion. The idea is to provide a data access layer on top of unified data model. It is similar to the DAOs that we write on top of a RDBMS, but not the same. Let me explain by example for applications, - There will be one Application object used

Re: [Architecture] RXT Inheritance model for G-Reg 5.0.0

Hi Dimuthu, On Thu, Aug 7, 2014 at 9:08 AM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi Subash, That was the conclusion of the discussion. The idea is to provide a data access layer on top of unified data model. It is similar to the DAOs that we write on top of a RDBMS, but not the

Re: [Architecture] RXT Inheritance model for G-Reg 5.0.0

Hi Subash, We are not writing the wrapper for APIs. APIM team is writing wrapper for APIs. Similarly data access layer for services will be provided by Greg/AS teams. I am thinking that for applications we'll have something like org.wso2.carbon.applications.*. There is nothing appfactory about

Re: [Architecture] RXT Inheritance model for G-Reg 5.0.0

Hi Subash, Looks good, but, can we change this to the following format, such that it remains compatible with the naming standards. 1. application/vnd.wso2.application+json name,version 2. application/vnd.wso2.application.mobile+json mobileType 3.