grouper-users - RE: [grouper-users] Web Service error condition catching
Subject: Grouper Users - Open Discussion List
List archive
- From: "Hyzer, Chris" <>
- To: "Black, Carey M." <>, Jeffrey Crawford <>
- Cc: Gouper Users List <>
- Subject: RE: [grouper-users] Web Service error condition catching
- Date: Wed, 13 Dec 2017 20:18:41 +0000
- Accept-language: en-US
- Authentication-results: spf=none (sender IP is ) ;
- Ironport-phdr: 9a23:CViGeBLhRSKvBfttN9mcpTZWNBhigK39O0sv0rFitYgfKvvxwZ3uMQTl6Ol3ixeRBMOHs6sC07KempujcFRI2YyGvnEGfc4EfD4+ouJSoTYdBtWYA1bwNv/gYn9yNs1DUFh44yPzahANS47xaFLIv3K98yMZFAnhOgppPOT1HZPZg9iq2+yo9JDffxhEiCChbb9uMR67sRjfus4KjIV4N60/0AHJonxGe+RXwWNnO1eelAvi68mz4ZBu7T1et+ou+MBcX6r6eb84TaFDAzQ9L281/szrugLdQgaJ+3ART38ZkhtMAwjC8RH6QpL8uTb0u+ZhxCWXO9D9QKsqUjq+8ahkVB7oiD8GNzEn9mHXltdwh79frB64uhBz35LYbISTOfFjfK3SYMkaSHJBUMhPSiJBHo2yYYgBD+UDPOZXs4byqkAUoheiGQWhHv/jxiNKi3LwwKY00/4hEQbD3AE4Ed4AsnTVrdTrO6cISey+0bfFzTXZb/NXwjfx5pXDfxckof6QXbJxccvQxlc1Fw7ej1WQspDqMymI1uQVrWeb6exgWfixhGE6tgF8uz6izdovhInRno8Z1E3I+CRjzIs7O9G0UlN3bN24HJdKqi2XNY97Tts/T2xmpCo20LkLtYOhcCQU1ZgqwwTTZ+GFfoWJ5B/oSfyfLi1ihH1/fbKynxay/lakyu37TsS6yEpHoC1ZntXRr3wAygTd58aeRvt65UiuxyyD1wfO6uFYOk80krfbK5g8zbIqjpoTq0PDHjPol0rqkK+Wd0Ik+u6y5+Tgf7XmupucN4hzigH9KKghhsu/AeEgPggPWWiU5/i82aX98UHkQbhGlPM7nrfDvJzHJskXurS1DxJX34sn8xq/Ci2p0NUcnXkJNlJFfxeHgpDsO17SIPD5Dfa+jEq2kDpwxvDGJaHuDo/QLnjbjrjhe7B951RCxwUu0NBT/4hUBa0ZIPLvRk/xs8TVDhAjMwyz3ubnEMty1pkHVWKSGa+WLrnSsUST6+IrIumMf5MVuC3jJ/Q/5v7ui2M5lkEHfamvw5QXdG60Eu54LEqEfHq/yusGRC0gugM1T6iio1SYXC8bQjD4F/Y24jgwC8T/V9zrQZuwxrGNwXH/Vr9baG5cB0HEOm3haIuDQftEPCCfLMF7ny0PfaWqUIRn2B2z4lzU0b1ie6D06z8Vr9ar/9hv5vaZ3UU3/jxlHcmH+2CWRCdphm4OQXk70L0p8h818UuKzaUt268QLtdU/f4cF15ibZM=
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
Rest and soap return the same elements… you don’t have to request the metadata, it will be sent. Thanks Chris From: [mailto:]
On Behalf Of Black, Carey M. Jeffrey Crawford, It looks like Jeff McCullough can get back a thrown Java exception message. Maybe you (Jeffrey) are not seeing your message due to how you are calling the Web Service? ( I have not tested this…. ) I reviewed the v2_3?wsdl and it looks like ( at least in the SOAP based calls ) there may be a way to get this kind of information in the returned response. I am look at this part: “ <xs:complexType name="WsResultMeta"> <xs:sequence> <xs:element maxOccurs="unbounded" minOccurs="0" name="params" nillable="true" type="ns:WsParam"/> <xs:element minOccurs="0" name="resultCode" nillable="true" type="xs:string"/> <xs:element minOccurs="0" name="resultCode2" nillable="true" type="xs:string"/> <xs:element minOccurs="0" name="resultMessage" nillable="true" type="xs:string"/> <xs:element minOccurs="0" name="success" nillable="true" type="xs:string"/> </xs:sequence> </xs:complexType> “ You may not be requesting the meta results in your calling of the Web Service? Maybe the REST form does not return the same meta data? ( I have not checked… but I hope it would be there too….) Just a few thoughts. ( Again, I have not tested my ideas out.) HTH. --
Carey Matthew
From:
[]
On Behalf Of Jeffrey Crawford Yes group name uniqueness is installed, however it seems like the failure is the same kind of failure you get if you don't have permission to create the new group. This is making informing the
user the reason why difficult. Is there some sort of status a web service could query? I suppose one could check if the group exists but wouldn't they need to try all the different cases? or can the web service search for a group in a case insensitive way?
(Sorry I don't use the WS much myself) I don't think getting a list of all groups to parse is very feasible since the list is very large. Is there really no message from the WS that informs the service as to why it failed, the UI says "The group ID is already
in use, please use a different ID" which seems to indicate that there is some way to do that. Thanks for your input
Jeffrey E. Crawford ^ ^ / \ ^ / \ ^ / \/ \ / \ / \ / \/ \/ \ / \ You have been assigned this mountain to prove to others that it *can* be moved. On Tue, Dec 12, 2017 at 12:03 AM, Hyzer, Chris <> wrote:
|
- [grouper-users] Web Service error condition catching, Jeffrey Crawford, 12/04/2017
- [grouper-users] Re: Web Service error condition catching, Jeffrey Crawford, 12/11/2017
- Re: [grouper-users] Web Service error condition catching, Jeff McCullough, 12/11/2017
- RE: [grouper-users] Web Service error condition catching, Hyzer, Chris, 12/12/2017
- Re: [grouper-users] Web Service error condition catching, Jeffrey Crawford, 12/12/2017
- RE: [grouper-users] Web Service error condition catching, Black, Carey M., 12/12/2017
- Re: [grouper-users] Web Service error condition catching, Jeffrey Crawford, 12/12/2017
- RE: [grouper-users] Web Service error condition catching, Hyzer, Chris, 12/13/2017
- Re: [grouper-users] Web Service error condition catching, Jeffrey Crawford, 12/18/2017
- RE: [grouper-users] Web Service error condition catching, Black, Carey M., 12/12/2017
- Re: [grouper-users] Web Service error condition catching, Jeffrey Crawford, 12/12/2017
- RE: [grouper-users] Web Service error condition catching, Hyzer, Chris, 12/12/2017
- Re: [grouper-users] Web Service error condition catching, Jeff McCullough, 12/11/2017
- [grouper-users] Re: Web Service error condition catching, Jeffrey Crawford, 12/11/2017
Archive powered by MHonArc 2.6.19.