EclipseLink has support for appending additional criteria to queries.
See,
http://wiki.eclipse.org/EclipseLink/UserGuide/JPA/Basic_JPA_Development/Mapping/Additional_Criteria
EclipseLink also supports VPD, see,
http://wiki.eclipse.org/EclipseLink/Examples/JPA/Auditing
ljnelson wrote:
Has the EclipseLink team (and the JPA spec leads) seen the JPA security
project? You can find it here: http://jpasecurity.sourceforge.net/
Perhaps it is common knowledge, but I just ran across it yesterday and am
intrigued.
I am about to get embroiled here at work in a lot of fine-grained,
instance-level security use cases. I would like to find an approach that
treats this kind of access as an aspect or layer of the system, rather
than
one that requires me to carefully inject dynamic WHERE clauses in my
hundreds of JPQL queries (as an example).
I would be curious to know where in the JPA roadmap (with multitenancy
etc.) this kind of instance-level security falls.
Thanks for any input.
Best,
Laird
--
http://about.me/lairdnelson
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
-----
http://wiki.eclipse.org/User:James.sutherland.oracle.com James Sutherland
http://www.eclipse.org/eclipselink/
EclipseLink , http://www.oracle.com/technology/products/ias/toplink/
TopLink
Wiki: http://wiki.eclipse.org/EclipseLink EclipseLink ,
http://wiki.oracle.com/page/TopLink TopLink
Forums: http://forums.oracle.com/forums/forum.jspa?forumID=48 TopLink ,
http://www.nabble.com/EclipseLink-f26430.html EclipseLink
Book: http://en.wikibooks.org/wiki/Java_Persistence Java Persistence
Blog: http://java-persistence-performance.blogspot.com/ Java Persistence
Performance