Hi Madawa, IMO, we do not need a separate media type handler for this. Reason being a media type handler for a REST call doesn't seem correct. Rather what we need is a method to take the URL etc to utilize the methods in WADL and swagger processor. WDYT??
Using existing swagger and WADL processor however seems the right approach for consistency without rewriting all the code again. Shazni Nazeer Mob : +94 777737331 LinkedIn : http://lk.linkedin.com/in/shazninazeer Blog : http://shazninazeer.blogspot.com On Fri, Apr 8, 2016 at 12:22 AM, Madawa Soysa <[email protected]> wrote: > Hi, > > I have started improving the REST Service artifact handling capability in > GREG[1] <https://wso2.org/jira/browse/REGISTRY-3532>. In the current > implementation, when a REST Service is added manually and if a Swagger or > WADL resource URL is given, the resource will not get uploaded to the > system and the relevant associations will not get created. The purpose of > this improvement is to fix the above issue. > > My approach to solving this issue is by writing a separate media type > handler to handle REST service artifact and use existing swagger and WADL > processors to import the specified resource. Any suggestions and feedback > are appreciated. > > > [1] - https://wso2.org/jira/browse/REGISTRY-3532 > > Regards, > Madawa > -- > > Madawa Soysa / Software Engineer > [email protected] / +94714616050 > > WSO2 Inc. > lean.enterprise.middleware > > [image: Twitter] <https://twitter.com/madawa_rc> [image: > LinkedIn] <https://www.linkedin.com/in/madawasoysa> [image: Github] > <https://github.com/madawas> [image: Tumblr] <http://madawas.tumblr.com/> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
