Skip to Content.
Sympa Menu

grouper-dev - RE: [grouper-dev] custom Grouper UI development

Subject: Grouper Developers Forum

List archive

RE: [grouper-dev] custom Grouper UI development

Chronological Thread 
  • From: "Hyzer, Chris" <>
  • To: Scott Koranda <>, "" <>
  • Subject: RE: [grouper-dev] custom Grouper UI development
  • Date: Sun, 3 Jul 2016 17:02:57 +0000
  • Accept-language: en-US
  • Authentication-results: spf=none (sender IP is ) ;
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

If you used the grouper java API (non WS) which is what the Grouper UI does,
there is more flexibility on the types of queries and the speed of
processing. If it is a simple UI, use WS. If there are gaps in
functionality, and you cant do it, then use the API. Ok?


-----Original Message-----

On Behalf Of Scott Koranda
Sent: Friday, July 01, 2016 9:25 AM

Subject: [grouper-dev] custom Grouper UI development


Suppose one was developing a "custom UI" for Grouper. One
obvious architecture is to have the UI invoke Grouper web
services (WS).

If the custom UI itself will be built using Java, is there a
Grouper Java API that one should use instead? What would be
the benefits and tradeoffs of developing against the Java API
instead of against the WS?


Scott K

Archive powered by MHonArc 2.6.19.

Top of Page