I am able to bind odatav2.0 with UI5 (e.g. Master-Detail Fiori or sap.tnt tool-page-app) in case of the OData (v2) producer (with mock-data) back-end (Java web app) running on an external tomcat server (packaged as "war" configured through pom).
But, my real backend OData producer is a Spring-Boot Java application (embedded tomcat within Spring-Boot, packaged as "jar" configured through pom, business data fetched from NoSQL MongoDB using spring-data-mongodb and converted to odata entities exposed through CXFNonSpringJaxrsServlet in case of apache olingo library odata v2.0 and HttpServlet in case of olingo odata v4.0), which is not consumed from the UI5 apps even though the data-binding is configured in the same way.
So, my question is there any particular guideline to develop the odata-provider in a specific way so that the UI5 apps can consume the odata?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.