Skip to Content.
Sympa Menu

grouper-dev - RE: [grouper-dev] Code for simplified UI

Subject: Grouper Developers Forum

List archive

RE: [grouper-dev] Code for simplified UI


Chronological Thread 
  • From: Rob Hebron <>
  • To:
  • Subject: RE: [grouper-dev] Code for simplified UI
  • Date: Mon, 12 Oct 2009 09:20:11 +0100
  • Importance: Normal
  • Sensitivity:

We're getting some hosting sorted for it here at Cardiff this week. It'll
take me another week or so to remove any domain-specific stuff, publish and
document it. After that I'll link to it on the Wiki.

Rob


-----Chris Hyzer
<>
wrote: -----

To: Rob Hebron
<>,

""
<>
From: Chris Hyzer
<>
Date: 10/09/2009 04:02AM
Subject: RE: [grouper-dev] Code for simplified UI


> 1. developed a new, simplified UI for end users built on Spring webflow

Great.  Even better if you have some screenshots or a screen movie which
shows it in action.  :)


> 2. used the hooks in the API to synchronise data held in Grouper with
> the
> LDAP directories used in the University (Novell eDirectory). An open
> source
> ESB (Mule) and rules engine (Drools) is used to do this as a 2-way sync

Sounds very interesting.  We have now three ways to do this (after 1.5 /
1.5.1 / 1.6) is released:

1. Hooks
2. Change log
3. ldappc ng

Maybe we should publish a wiki page with the pro's / con's of each approach
with examples (including yours).


> The code we've developed can all be made available as open source, and
> we'd
> very much like to do so if there is interest. From the point of view of
> Grouper developers, what would be the best way to go about this? I plan
> to
> keep maintaining the code, but is there somewhere where should it live,
> or
> be linked from, so it would be of most benefit?

We should definitely link at lease from the contrib. page (can you request
access from Steve Olshanky steveo AT internet2 DOT edu).  Tom Barton
probably has better information architecture ideas about where things
should live.  :)

Chris




Archive powered by MHonArc 2.6.16.

Top of Page