Subject: Grouper Users - Open Discussion List
- From: "Hyzer, Chris" <>
- To: Suresh Marru <>, "" <>
- Subject: RE: [grouper-users] Java vs WS API
- Date: Sun, 8 May 2016 22:05:03 +0000
- Accept-language: en-US
- Authentication-results: apache.org; dkim=none (message not signed) header.d=none;apache.org; dmarc=none action=none header.from=isc.upenn.edu;
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:23
Generally institutions use the WS though in your case maybe the java API is better. You can also perform readonly queries from the DB views.
Javadoc is here: http://internet2.github.io/grouper/
Some of the API is described here: https://spaces.internet2.edu/pages/viewpage.action?pageId=14517859
There are Save objects and Finder objects e.g. GroupSave and GroupFinder. Since most people use the WS, the Java API is not all that well documented, but let us know your questions and we can answer them and update the wiki.
MySQL is probably best for you.
We are exploring to use Grouper for group management within Apache Airavata. We will not be using the grouper UI, but just the group management features from a java library.
Can we directly use the Java API or is it recommended to use the web service deployment and use the WS Client?
If the Java API can be directly used, what is the recommended Jar from the list - http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22edu.internet2.middleware.grouper%22
Is there a publicly hosted Java API documentation?
What is recommended production database to be installed with grouper?
- [grouper-users] Java vs WS API, Suresh Marru, 05/07/2016
- RE: [grouper-users] Java vs WS API, Hyzer, Chris, 05/08/2016
Archive powered by MHonArc 2.6.16.