Announcement Announcement Module
Collapse
No announcement yet.
AfterInvocationProvider and parent/child relationship Page Title Module
Move Remove Collapse
This topic is closed
X
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • AfterInvocationProvider and parent/child relationship

    What the best way filter child objects?
    Suppose we added
    Collection subContacts;
    property into Contact class. How this collection will be filtered? I mean if we have the following hierarchy:
    - Contact1
    -- Contact2
    -- Contact3
    - Contact4

    and user has permission on all contacts except Contact3. In this case getSubContacts() has to return collection only with Contact2 instance (without Contact3). How it will be works if dao level return Contact1 instance with {Contact2,Contact3} sub-contacts already. How to filter it?
    How I understand BasicAclEntryAfterInvocationCollectionFilteringPro vider and BasicAclEntryAfterInvocationProvider not enough here. What the best way to customize this behaivor?

  • #2
    Originally posted by mpetrashev
    How I understand BasicAclEntryAfterInvocationCollectionFilteringPro vider and BasicAclEntryAfterInvocationProvider not enough here. What the best way to customize this behaivor?
    You're right, these classes cannot navigate into your domain objects' specialised properties.

    You could enhance these classes to reflect the domain object, locate any arrays or Collections, and then re-apply the filtering logic. I'll add this idea to JIRA: http://opensource.atlassian.com/proj.../browse/SEC-16

    Comment

    Working...
    X