Skip to Content.
Sympa Menu

grouper-dev - RE: [grouper-dev] Action Items: Grouper-Dev Call 9-Jul-2008

Subject: Grouper Developers Forum

List archive

RE: [grouper-dev] Action Items: Grouper-Dev Call 9-Jul-2008

Chronological Thread 
  • From: Chris Hyzer <>
  • To: Tom Barton <>
  • Cc: "" <>
  • Subject: RE: [grouper-dev] Action Items: Grouper-Dev Call 9-Jul-2008
  • Date: Thu, 10 Jul 2008 11:22:21 -0400
  • Accept-language: en-US
  • Acceptlanguage: en-US

> How is the sequence of hook firing determined? What if a hook must be
> last, or first, or must override others?

Well, right now there is no ordering. I mean, it is kept ordered, and it is
deterministic so each time you start grouper it will be the same order, but
its hard to tell if a suite hook will be before or after a configured hook.

I would like to see a use case where it matters though. I have a hope deep
down that it doesn't matter too much. I think things like auditing will be a
post hook, and you shouldn't edit the object in a post hook, so any order in
the post hook world would be equivalent, right?

I think the ordering matters when in the pre-hook when the data is being
edited, and I don't know of any built-in pre-hooks where we edit the data,
and if the institution is writing multiple editing pre-hook, they can do the
original method where they write all their logic in one hook and order it
themselves. Or if you register multiple hooks via the config file
(non-suite), then the hooks will execute in the order entered.

We could add a priority to the hooks if there is a need [no problem], but if
we can avoid that extra complexity it would be nice.


Archive powered by MHonArc 2.6.16.

Top of Page