What is the endpoint you are trying for the importer?
Also, trying to understand, what you are doing
Teiid Designer --> OData Importer --> Teiid Odata --> Teiid VDB --> Teiid Web Service --> Teiid Procedure --> Some Source ?
What is the intention behind importing the odata from teiid?
Thanks for the reply.
This is the end point I am using - http://localhost:8080/odata/booksWebSvc.1/ , though I tried with few other combinations also.
I am exactly doing Teiid Designer --> OData Importer --> Teiid Odata --> Teiid VDB --> Teiid Web Service --> Teiid Procedure --> Some Source
I have CRUD operations defined in my Teiid webservice model and able to consume the operations through SOAP/REST clients.
I am interested to know if I can and how to consume these webservices model operations through OData.
I get exception when I try to create a Teiid OData importer connection - org.jboss.resteasy.spi.NotAcceptableException: No match for accept header
When I try consuming them as any function imports I get "ServerErrorException with message Cannot infer EdmType for java type: org.teiid.core.types.SQLXMLImpl"
*All* VDBs deployed in the Teiid already expose OData interface. Why you need to re-import into a separate VDB? read the OData support in Teiid here OData Support - Teiid 8.8 (draft) - Project Documentation Editor
BTW, web services is additional layer on top of the VDB, much like OData, it adds the web access layer over your procedure, not any business logic. Your procedure is the main artifact that handles all your CRUD operations, so when using OData it does not go through Web Service layer, but works directly on top of your procedure, thus avoiding the additional web layer. For doing CRUD operations, you do not need to define the procedures, just define your views and provide the insert/update/delete transformations as needed, then use OData to issue the read/update/delete operations as described in the link I provided above.
As per the exception above if you can give a test case, I can re-test, but that seems to be a bug. Import process should have worked as expected, even though that is verbose as I explained above.