Hi Json, Here are some of my thoughts on basic requirements we should have as RAML support,
As an API Publisher I should be able to, - Attach a valid RAML file (Reject if it is not a valid RAML). You can use the following parsers according to the requirement that you should validate it in the client side or the server side (JS parser or the Java parser). - Edit the RAML file - Graphical view of the API describing by RAML file As an API Subscriber I should be able to, - View the RAML file of an API - Graphical view of the API describing by RAML file - RAML file should accessible as an URI to use in any tool to invoke the API directly (API Designer RAML console, SoapUI RAML Plugin) or generate code for invoking API (JAX-RS Codegen). Here RAML baseUri should be API Gateway URI not the original REST API base uri. Hope this helps. thanks Eranda On Monday, April 7, 2014, Jason Catlin <[email protected]> wrote: > Hey Guys, > > I'm looking into RAML/API Manger integration. > > So the first thing that I'm just a little confused about is that I'm > not excatly sure what deep processing of RAML will be done by the API > Manager. > > when the API Manger presents a WSDL, for instance, it doesn't actually > really look inside it; it just uploads the WSDL given by the user and > presents it to the API consumer. > > So, it's not really clear to me how RAML should be any different. > Won't the APIM just take the user's RAML and give it to the API > consumer? People keep seeming to imply that there will be some sort > of deeper processing involved, but I can't figure out what that is. > > In an earlier email, Joe Fonseka mentioned backend resource > definitions. But, I've read through this http://raml.org/spec.html > pretty carefully, and RAML doesn't specify backing resources. It's an > interface definition language. So we can't get the backend resources > from RAML. > > I'm sure we could extract a few things like names and descriptions, > but remember that this wouldn't really involve any deep processing of > the RAML. I mean, if that's what we want, fine, but just saying. > > jc > _______________________________________________ > Architecture mailing list > [email protected] <javascript:;> > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- *Eranda Sooriyabandara*Senior Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
