Grouper Users - Open Discussion List

[Chris Hyzer <>]

This is probably a can of worms, but originally people (not me) had an idea of XHTML response being used to make a web app out of the WS, and I don’t think that ever really materialized (now we have xhtml responses with no buttons so its not really all that useful).  So I would recommend we set the default of formatting of the rest-like services to be XML or JSON.  You can change this default in the grouper-ws.properties if you need backwards compatibility.  The reason for the change is by default people see XHTML which is not really all that usable programmatically and it takes time to figure out how to change it.  One problem is half the people probably think XML should be the default, and half think JSON.  I personally don’t care as long as it is not XHTML… J  Maybe we can discuss at the dev call tomorrow or if you want to send votes to me off list (or on or whatever) that would be great.

 

Thanks,

Chris

 

From: [mailto:] On Behalf Of Klug, Lawrence
Sent: Tuesday, June 19, 2012 2:40 PM
To:
Subject: [grouper-users] Consuming Grouper Web Services

 

Wrote a demo app that performs Grouper REST calls using Spring RESTTemplate.  The response is XHTML and I’m finding it difficult to parse.

 

Is there a better approach to the scenario – calling Grouper Web Services from a java program?

 

Thanks,

 

Lawrence