Vincenzo, The current snapshot version gives access to request object via the ODataContext class:
https://issues.apache.org/jira/browse/OLINGO-26 To hook into JPA processor implementation my idea would be to derive from ODataJPAProcessor (api) and re-implement the behavior of ODataJPAProcessorDefault (core) and add here your security checks. Maybe Chandan can hook in here. I have never tried this scenario and you have to try out. If it leads to success then good :) if not then continue this discussion. Regards, Stephan On 13.12.13 10:54, "Vincenzo Turco" <[email protected]> wrote: >Hi all, >I have exposed my JPA entities through the JPA processor and it works >great. >Now I have added authentication to my oData service, through the >appropriate configuration in web.xml. >I would like to restrict the entries returned by the odata service >according to the logged in user. >Is there any way to hook up custom logic (e.g. in the JPA processor) to do >so? >Also any alternative solution would be greatly valued. >Thanks a lot for your time and attention >Regards >Vincenzo > > >-- > > >Vincenzo Turco
