Thanks for suggestion. Will look into XmlSaxTableDef and get back to you Regards, Vijay Kumar J
-----Original Message----- From: Du Krøger, Dennis [mailto:[email protected]] Sent: Monday, June 20, 2016 1:31 PM To: [email protected] Subject: RE: MetaModel REST connector Errr, that's "XmlSaxTableDef" :) -----Original Message----- From: Du Krøger, Dennis [mailto:[email protected]] Sent: 20. juni 2016 08:49 To: [email protected] Subject: RE: MetaModel REST connector Hi Vijay, Probably not a completely satisfactory answer, but I'd take a look at the XxmSaxTableDef, which uses XPath definitions to make up the tables. I've been imagining something similar with JsonPath before, but you'd probably have do something else (but maybe similar?), since you need to point to Swagger entries instead, and require support for full CRUD. Best regards, Dennis -----Original Message----- From: Vijay Kumar Jalagari [mailto:[email protected]] Sent: 18. juni 2016 00:44 To: [email protected] Subject: MetaModel REST connector Hi, I am doing POC on Apache metamodel for one of our requirement in project and most of things are achievable using apache metamodel and its really a generic data processing application. Apart from database and file format we need to support the REST API as connector and since REST doesn't follow any schema definition we are planning to add swagger based custom connector in apache metamodel. Today I have started understand the swagger schema and its structure but it's quite difficult to visualize the swagger as RDBMS ( schema, tables and columns ) which is first requirement to write a connector in apache metamodel. Initial thought on converting swagger as connector 1. Convert all the operation ( paths ) as schema 2. and each Method type like GET, POST etc. as table 3. Method input & output as columns But problem with above approach method type are specify an operation type i.e. GET for Reading data, POST for writing back data, DELETE for deleting information so its doesn't make sense in visualize method type as table which may not provide all the operation like select, insert, update etc. over it. Another problem is input & output properties as schema which make create lot of confusion. Since you have written core and connector in apache metamodel can you please provide some suggestion in writing this REST connector ? Thanks & Regards Vijay Kumar J
