Hi all, AFAIU the question is about.
Option 1: Not using a standard API but inventing your way of parsing the RXT configuration. VS Option 2: Using a Standard API exposed by G-Reg. I would definitely go for #2. However, I'm not sure whether the APIs we have to date can facilitate what's needed. Sameera, can you please outline what functionality around the RXT do you expect to have? Is it simply CRUD operations for assets? If so, the WS-APIs are sufficient, or do you have more in mind? Thanks, Senaka. On Wed, Jul 24, 2013 at 4:17 PM, Ajith Vitharana <[email protected]> wrote: > > > > On Wed, Jul 24, 2013 at 3:32 PM, Ruchira Wageesha <[email protected]>wrote: > >> On Wed, Jul 24, 2013 at 2:46 PM, Sameera Medagammaddegedara < >> [email protected]> wrote: >> >>> Hello Everyone, >>> >>> We are attempting to ; >>> >>> 1. Locate all available artifacts (RXT) in the Governance Registry >>> 2. Generate a UI to facilitate creation of new artifacts (Create, >>> View, Delete and Update) inside a Jaggery application >>> >>> We have reached an impasse in determining how best to generate the UI.The >>> available options we have located so far are given below; >>> >>> *Option 1* >>> Read and pass the RXT file. >>> >> Only concern I had regarding this was, how to read the RXT definitions >> in a distributed deployment. Anyway, as RXT definitions are copied from >> file system to the registry, we should be able to read from there instead >> of reading from the file system. Once we have the rxt content in the >> Jaggery application, then RXT UIs can be generated by reusing the way which >> GReg uses. >> > > RXTs already stored in registry. > /_system/governance/repository/components/org.wso2.carbon.governance/types > > Thanks > Ajith. > >> >>> *Option 2* >>> Pass the WSDL file generated by the Governance Registry [1][2]. >>> >>> *Question* >>> What would be the ideal choice? Have we missed any other options? >>> >>> *References;* >>> >>> [1] CRUD operation support for Governance Artifacts,* URL: * >>> http://docs.wso2.org/wiki/display/Governance453/CRUD+operation+support+for+Configurable+Governance+Artifacts >>> >>> [2] Configurable Governance Artifacts (RXT), *URL: * >>> http://docs.wso2.org/wiki/pages/viewpage.action?pageId=16191336 >>> >>> Thank You, >>> Sameera >>> >> >> >> >> -- >> *Ruchira Wageesha >> **Associate Technical Lead* >> *WSO2 Inc. - lean . enterprise . middleware | wso2.com* >> * >> email: [email protected], blog: ruchirawageesha.blogspot.com, mobile: +94 >> 77 5493444* >> >> >> >> -- >> *Ruchira Wageesha >> **Associate Technical Lead* >> *WSO2 Inc. - lean . enterprise . middleware | wso2.com* >> * >> email: [email protected], blog: ruchirawageesha.blogspot.com, mobile: +94 >> 77 5493444* >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Ajith Vitharana. > WSO2 Inc. - http://wso2.org > Email : [email protected] > Mobile : +94772217350 > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- * <http://us13.wso2con.com/> * * * *Senaka Fernando* Senior 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
