Hi,
How about using the component tHttpRequest which meet some aspect needs of OData.
Best regards
Sabrina |
It seems that OData is not yet understood on Talend side. Support for OData of course means not only supporting OData acting as a client, but also acting as a server. OData is an exciting new technology that will make many of the small synch-solutions unnecessary by providing on the fly integration between enabled systems. Our expectation of course would be that Talend provides the ability to encapsulate an existing old system and exposing an OData interface.
An example szenario: Microsoft Dynamics CRM latest release supports OData, and SAP Netweaver latest releaese supports OData. In order to view invoices in the CRM, which is a not so often used function and does not require a data sync between the two systems we can configure the OData interface exposed by Netweaver in the CRM client. The client is then able to integration SAP invoice objects as if it were local objects, and Talend is out of the game - no Talend needed. At least it would be nice, if Talend could expose such interfaces towards Microsoft CRM, just like SAP Netweaver is capable doing. With leading ERP and CRM systems supporting OData, there is a emerging demand for OData like integration patterns, and for encapsulating legacy systems using OData patterns.
OData is now such a big trend in integration ... an no awareness on Talend side?
