Skip to Content.
Sympa Menu

grouper-dev - RE: [grouper-dev] [ldappcng] changelog entry hierarchy ?

Subject: Grouper Developers Forum

List archive

RE: [grouper-dev] [ldappcng] changelog entry hierarchy ?


Chronological Thread 
  • From: Chris Hyzer <>
  • To: Tom Zeller <>, Shilen Patel <>
  • Cc: Grouper Dev <>
  • Subject: RE: [grouper-dev] [ldappcng] changelog entry hierarchy ?
  • Date: Fri, 14 Oct 2011 20:10:03 +0000
  • Accept-language: en-US

I wonder what the pros and cons are of configuring it in XML like you have
below vs an expression language scriptlet ala Rob's ESB connector. This
isn't the real syntax, but something like this:

${entry.action == 'deleteMembership' && entry.enclosingAction !=
'deleteGroup'}

Thanks,
Chris

-----Original Message-----
From:


[mailto:]
On Behalf Of Tom Zeller
Sent: Wednesday, October 12, 2011 9:40 PM
To: Shilen Patel
Cc: Grouper Dev
Subject: Re: [grouper-dev] [ldappcng] changelog entry hierarchy ?

> new
> UserAuditQuery().setExtraCriterion(Restrictions.eq(AuditEntry.FIELD_CONTEXT
> _ID, contextId)).execute();

Thanks, it would have taken me awhile to figure that out.

So, for better or worse, I am using a shib attribute resolver data
connector to expose the changelog, i.e. a ChangeLogDataConnector. Here
is how I think we can express in xml the processing of changelog
membership deletions, ignoring those that are the result of a group
deletion :

<resolver:DataConnector id="deleteMembership"
xsi:type="grouper:ChangeLogDataConnector">
<grouper:Filter xsi:type="grouper:MINUS">
<grouper:Filter xsi:type="grouper:ChangeLog"
category="membership" action="deleteMembership" />
<grouper:Filter xsi:type="grouper:Audit" category="group"
action="deleteGroup" />
</grouper:Filter>
</resolver:DataConnector>

( One or both of the category and action attributes should be present.
The MINUS filter matches if the first child filter matches but the
second child filter does not. )

I need to do some code refactoring to extend this syntax to the
changelog, currently the <grouper:Filter /> elements are supported
just for groups, e.g.

<resolver:DataConnector id="testFilterMinus"
xsi:type="grouper:GroupDataConnector">
<grouper:GroupFilter xsi:type="grouper:Minus">
<grouper:GroupFilter xsi:type="grouper:StemName"
name="parentStem" scope="ONE" />
<grouper:GroupFilter xsi:type="grouper:ExactAttribute"
name="name" value="parentStem:groupB" />
</grouper:GroupFilter>
</resolver:DataConnector>

It will probably take me a half day to do this, I started refactoring
in Denver at jasig, but never committed.

TomZ



Archive powered by MHonArc 2.6.16.

Top of Page