On Aug 27, 2012, at 10:50 PM, Amila Jayasekara <thejaka.am...@gmail.com> wrote:
> On Mon, Aug 27, 2012 at 10:16 PM, Saminda Wijeratne <samin...@gmail.com> > wrote: >> Any particular reason why Registry API is used as an initial impl? > > Hi Saminda, > > There is already a rest implementation written for workflow execution. > That is one reason why we thought of implementing a rest interface for > registry API. > Further, when invoking a workflow there are considerable amount of > parameters which we have to pass. So it is a bit debatable whether > REST is the suitable technology to expose WF execution. Cos it is easy > to generate a client program using WSDL when exposed as a web service. > But it makes sense to have REST interface to registry, as the exposed > operations are sort of directly mapped to rest operations and > resources are also well defined. (We had a brief discussion about this > in the morning) > > Appreciate community views on this also. + 1, I fully agree with your observation Amila, Its not always a REST vs SOAP. It really depends on the context and I concur in this case registry and information services fully make sense for having a RESTful interface but I wonder the justification of REST for complex needs like workflow configurations and passing in all the context and QOS. BTW, since Interpreter server run as a Axis2 service, is the REST support provided by axis2 not enough? Suresh > On a side not the term "Airavata API" is a bit confusing. Even though > we say it is an API, it sits in the client side and directly makes > calls to JackRabit DB. So we believe there should be a proper > separation between API and client code. Another discussion point was > to make available a REST API and talk to JackRabit through the API > (using Java method calls). This will also improve the performance. > > Thank you > Regards, > AmilaJ > > >> >> Saminda >> >> On Mon, Aug 27, 2012 at 9:31 PM, Chathuri Wimalasena >> <kamalas...@gmail.com>wrote: >> >>> Hi Devs, >>> >>> We are planing to add a REST interface for Airavata Registry API. There are >>> several REST frameworks that are compatible with JAX-RS. Some examples are >>> RESTEasy [1], Jersey [2] etc. IMO it is better to use Jersey since it has a >>> REST client and it is used by many other apache projects as well. >>> >>> In order to have the REST API integrated, we need a web container which >>> should be embedded in to Airavata. But for the initial implementation, we >>> can use an external tomcat server as the web container. As initial >>> approach, we will implement basic functions of the Registry API and >>> continue to iterate over it. >>> >>> Your suggestions are welcome. >>> >>> Thanks and Regards, >>> Chathuri >>> >>> [1] http://www.jboss.org/resteasy >>> [2] http://jersey.java.net/ >>>
