On Thu, Oct 2, 2014 at 9:55 PM, Isuruwan Herath <[email protected]> wrote:
> > - Discussed to introduce the attribute "Interface Type" for service > metadata model. This will record the interface which it gets exposed (ex: > swagger/wsdl/wadl). The reference will be the UUID of the interface > document resource in registry (ex: swagger doc file). TBD what should we > use as the media type for swagger docs (define one?). > - Also discussed about capturing the Service implementation artifact or > packaging model. > FYI : Regarding mime type for swagger there is a pending proposal in community refer [1] [1] https://github.com/wordnik/swagger-spec/issues/110 Thanks Jo > > > On Fri, Sep 19, 2014 at 9:31 AM, Dimuthu Leelarathne <[email protected]> > wrote: > >> hi all, >> >> We had a meeting yesterday regarding the WSO2Con demo. >> >> Participants - Nuwan, Joe, Subash, Manjula, Dimuthu >> >> Here are the notes of the meeting. >> >> 1 - When a service is promoted to production, when an API creation >> wizard will have a drop down of JAX-RS service endpoints when HTTP end >> point is selected >> 2 - When the service is retired, what happens? Manually remove it from >> API cloud for Con. >> >> But in the future when an API is removed, >> a - We have to automatically remove the API from Gateway. For that >> Registry needs to give a listener interface >> b - We need to warn the user saying there is an API published we are >> going to remove it as well. As a usability measure >> >> >> thanks, >> dimuthu >> >> >> >> >> >> >> >> On Fri, Sep 19, 2014 at 8:30 AM, Dimuthu Leelarathne <[email protected]> >> wrote: >> >>> Hi, >>> >>> We do check items using API. I don't know what approval votes are. >>> >>> thanks, >>> dimuthu >>> >>> >>> On Fri, Sep 19, 2014 at 12:36 AM, Subash Chaturanga <[email protected]> >>> wrote: >>> >>>> Hi Dimuthu, >>>> Does AF currently doing check item/approval votes programatically for >>>> life cycles using registry API ? >>>> >>>> On Thu, Sep 18, 2014 at 3:06 PM, Subash Chaturanga <[email protected]> >>>> wrote: >>>> >>>>> Hi Sanjiva, >>>>> Based on previous discussions, we came to a conclusion that super >>>>> types should have a version. *Service > ServiceVersion. In that case, >>>>> what >>>>> about super types like Endpoint ? Because version for an endpoint is not >>>>> make sense IMO. As per the doc, we agreed to create a separate type for >>>>> endpoint ? >>>>> >>>> >>>> >>>> >>>> -- >>>> Thanks >>>> /subash >>>> >>>> *Subash Chaturanga* >>>> Senior Software Engineer & Lead WSO2 Governance Registry >>>> Platform TG; WSO2 Inc. http://wso2.com >>>> Contact: >>>> email: [email protected] >>>> blog: http://subashsdm.blogspot.com/ >>>> twitter: @subash89 >>>> phone: +9477 2225922 >>>> Lean . Enterprise . Middleware >>>> >>> >>> >>> >>> -- >>> Dimuthu Leelarathne >>> Architect & Product Lead of App Factory >>> >>> WSO2, Inc. (http://wso2.com) >>> email: [email protected] >>> Mobile : 0773661935 >>> >>> Lean . Enterprise . Middleware >>> >> >> >> >> -- >> Dimuthu Leelarathne >> Architect & Product Lead of App Factory >> >> WSO2, Inc. (http://wso2.com) >> email: [email protected] >> Mobile : 0773661935 >> >> Lean . Enterprise . Middleware >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Isuruwan Herath > Technical Lead > > Contact: +94 776 273 296 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- -- *Joseph Fonseka* WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 772 512 430 skype: jpfonseka * <http://lk.linkedin.com/in/rumeshbandara>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
