Hi Kasthuriraajan, This project would be a combination of both DB Lookup and DB Report [1] <https://docs.wso2.com/display/EI611/DB+Report+Mediator> mediators in WSO2 EI to support all CRUD operations with additional capabilities (eg: retrieving multiple rows as the result element). Therefore, I think it would be better if we can use a functionality specific name rather than an existing mediator specific name.
Thanks, Prabushi [1] - https://docs.wso2.com/display/EI611/DB+Report+Mediator On Sat, Feb 17, 2018 at 7:11 AM, Gayan Dhanushka <[email protected]> wrote: > Hi Kasthuriraajan, > > If we can improve the DBLookup mediator to retrieve more than a single row > in a database I think that is definitely an improvement. > > If you are implementing this improvement, it seems to me like the name > "DSS-Call" is a bit misleading since we will not be doing an actual call. > > How about something like "ExtendedDBLookup" or something similar ? > > I am not clear on whether all the CRUD operations be supported with this > mediator. Then we would need to use a different name altogether. > > +1 for the idea of bypassing the transport layers and directly talking to > the data service components to execute the queries. > > Regards > Gayan > > On Fri, Feb 16, 2018 at 1:25 AM, Kasthuriraajan Ratnasingam < > [email protected]> wrote: > >> >> >> Hi all, >> >> I am working on a project to implement a DSS-call mediator . >> >> >> * If we need to consume DSS service from an ESB sequence, we have to do a >> HTTP call using send or call mediator (just like any other remote HTTP >> service). This is a very inefficient way as HTTP call will introduce an >> additional latency and performance overhead. EI product comes with DSS >> feature built in but there is no way to properly avoid remote HTTP call >> when calling data service which hosted in the same server. We can avoid the >> HTTP call using local transport in the EI. However axis2 service invocation >> overhead is still there and we need to build a new request payload to >> invoke DSS service even with local transport.Even local transport gives a >> better performance than HTTP call, it is not a fully optimized solution. >> That's why this new project idea to build new DSS-Call mediator which can >> do direct data service calls without going through send or call mediator >> and http request (in JVM DSS invocation). The new approach is to come up >> with a DBLookup mediator style invocation for data service. DBLookup >> mediator can fetch only one row of the result of a query. Because of that >> we are using data service. So that the new mediator should have the >> privileges to invoke all the facilities of a data service with the in JVM >> call. * >> Please give your comments and suggestions regarding this project. >> >> Thank you. >> >> Regards, >> R.Kasthuriraajan. >> >> -- >> R.Kasthuriraajan >> Software Engineering Intern | WSO2 >> LinkedIn: https://www.linkedin.com/in/ratnasingam-kasthurira >> ajan-2a6892121 >> >> Email: [email protected] >> Mobile : +94779893005 <+94%2077%20989%203005> >> Web: http://wso2.com <http://wso2.com/> >> >> > > > -- > Gayan Dhanuska > Senior Software Engineer > http://wso2.com/ > Lean Enterprise Middleware > > Mobile - LK- 071 666 2327 > Mobile USA - 612-244-4873 <(612)%20244-4873> > > > Office > Tel : 94 11 214 5345 > Fax : 94 11 214 5300 > -- *Prabushi Samarakoon* Software Engineer Mobile: +94715434580 Email: [email protected]
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
