The JPA Processor fills the gap between Olingo V4 and the database, by providing a mapping between JPA metadata and OData metadata, generating queries and supporting the entity manipulations.
Apache License 2.0
122
stars
76
forks
source link
Request few ways to know more about the implementation #241
Need some idea with the tutorials that we are seeing or how we are implementing we are using some kind of HttpServlet Request and HttpServlet Response to directly send or write to the PrintStream without getting a chance to intercept or modify the data, is there a way to intercept the data for conversion to DTOs and other processing (of course we could use filter or Wrapper to intercept) but one question like is, is it possible to make this in a way like we get the request from the controller and pass it to the Service layer and do steps like calling the OData DB client which on executing queries would result a Entity object with the data as called that would help in converting and the tailoring the request and send it to the end user,
Really like the out of box solution that is provided with this implementation, but we don't see this kind of implementation to do something like above mentioned, is this something not supported or is there something present that we are not using ?
Please help regarding this, on an urgent basis.
Need some idea with the tutorials that we are seeing or how we are implementing we are using some kind of HttpServlet Request and HttpServlet Response to directly send or write to the PrintStream without getting a chance to intercept or modify the data, is there a way to intercept the data for conversion to DTOs and other processing (of course we could use filter or Wrapper to intercept) but one question like is, is it possible to make this in a way like we get the request from the controller and pass it to the Service layer and do steps like calling the OData DB client which on executing queries would result a Entity object with the data as called that would help in converting and the tailoring the request and send it to the end user, Really like the out of box solution that is provided with this implementation, but we don't see this kind of implementation to do something like above mentioned, is this something not supported or is there something present that we are not using ? Please help regarding this, on an urgent basis.