grouper-users - wsStem vs WsStem in returned xml
Subject: Grouper Users - Open Discussion List
List archive
- From: Colin Hudler <>
- To: Grouper Users Mailing List <>
- Subject: wsStem vs WsStem in returned xml
- Date: Wed, 14 Jan 2009 11:01:16 -0600
When using RESTlite web-services, if I create a stem, it will return something like this:
<WsStemSaveLiteResult>
<resultMetadata>
<resultCode> "SUCCESS_INSERTED" </resultCode>}
[snip!]
</resultMetadata>
<responseMetadata>
<millis> "3653" </millis>
<serverVersion> "v1_4_000" </serverVersion>
</responseMetadata>
<wsStem>
<extension> "test" </extension>
[snip!]
</wsStem>
</WsStemSaveLiteResult>
But when I fetch a stem with findStem:
<WsFindStemsResults>
<stemResults>
<WsStem>
<extension> "test" </extension>
</WsStem>
</stemResults>
<resultMetadata>
<resultCode> "SUCCESS" </resultCode>}
</resultMetadata>
</WsFindStemsResults>
See how it is sometimes WsStem and others wsStem? This frustrates use of XPath, and I was wondering if a change would be considered. I can work around it, of course, by walking through the documents myself, or maybe using XPath transform. Any other suggestions are appreciated.
--
Colin Hudler
- wsStem vs WsStem in returned xml, Colin Hudler, 01/14/2009
- RE: [grouper-users] wsStem vs WsStem in returned xml, Chris Hyzer, 01/14/2009
Archive powered by MHonArc 2.6.16.