Tutorials Point


  UDDI Tutorial
  UDDI API References
  UDDI Resources
  Selected Reading

Copyright © 2014 by tutorialspoint



  Home     References     About TP     Advertising  

UDDI API - set_publisherAssertions

previous

Description: The set_publisherAssertions API call is used to manage all of the tracked relationship assertions associated with an individual publisher account.

Upon successful completion, a publisherAssertions message is returned containing all of the relationship assertions currently attributed to the publisher account that is associated with the authInfo data passed.

Version 2.0 Syntax:

<set_publisherAssertions generic="2.0" xmlns="urn:uddi-org:api_v2" >
     <authInfo/>
     [<publisherAssertion>
     <fromKey/>
     <toKey/>
     <keyedReference/>
     </publisherAssertion>...]
</set_publisherAssertions>

Arguments:

authInfo: This required argument is an element that contains an authentication token. Authentication tokens are obtained using the get_authToken API call.

publisherAssertion: zero or more relationship assertions. Relationship assertions consist of a reference to two businessEntity key values as designated by the fromKey and toKey elements, as well as a required expression of directional relationship within the contained keyedReference element.

Error Returned:

If any error occurs in processing this API call, a dispositionReport element will be returned to the caller within a SOAP Fault. The following error number information will be relevant:

E_invalidKeyPassed: signifies that one of the uuid_key values passed did not match with any known businessKey or tModelKey values. The assertion element and the key that caused the problem will be clearly indicated in the error text.

E_authTokenExpired: signifies that the authentication token value passed in the authInfo argument is no longer valid because the token has expired.

E_authTokenRequired: signifies that the authentication token value passed in the authInfo argument is either missing or is not valid.

E_userMismatch: signifies that neither of the businessKey values passed in the embedded fromKey and toKey elements is controlled by the publisher account associated with the authentication token. The error text will clearly indicate which assertion caused the error.



previous Printer Friendly

Advertisements


  

Advertisements