- UDDI Tutorial
- UDDI - Home
- UDDI - Overview
- UDDI - Elements
- UDDI - Technical Architecture
- UDDI - Data Model
- UDDI - Interfaces
- UDDI - Usage Example
- UDDI with WSDL
- UDDI - Implementations
- UDDI - Specifications
- UDDI - Summary
- UDDI API References
- UDDI - API Quick References
- UDDI Useful Resources
- UDDI - Quick Guide
- UDDI - Useful Resources
- UDDI - Discussion
- Selected Reading
- UPSC IAS Exams Notes
- Developer's Best Practices
- Questions and Answers
- Effective Resume Writing
- HR Interview Questions
- Computer Glossary
- Who is Who
UDDI API - save_service
The save_service API call adds or updates one or more businessService elements.
This API call returns a serviceDetail message containing the final results of the call that reflects the newly registered information for the effected businessService elements. In cases where multiple businessService elements are passed in the request, the result will contain the final results for each businessService passed and these will occur in the same order as found in the request. If the same entity is listed more than once in the save_service message, it may be listed once in the result for each appearance in the save_service message. If so, the last appearance in the results represents the final saved state.
Version 2.0 Syntax
<save_service generic = "2.0" xmlns = "urn:uddi-org:api_v2" > <authInfo/> <businessService/> [<businessService/>.] </save_service>
authInfo − This required argument is an element that contains an authentication token. Authentication tokens are obtained using the get_authToken API call.
businessService − One or more complete businessService elements can be passed. For the purpose of performing round trip updates, this data can be obtained in advance by using the get_serviceDetail API call or by any other means.
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_authTokenExpired − It signifies that the authentication token value passed in the authInfo argument is no longer valid because the token has expired.
E_authTokenRequired − It signifies that the authentication token value passed in the authInfo argument is either missing or is not valid.
E_invalidKeyPassed − It signifies that the request cannot be satisfied because one or more uuid_key values specified is not a valid key value. This includes any tModelKey references, as well as references to serviceKey or bindingKey values that either do not exist.
E_userMismatch − It signifies that one or more of the uuid_key values passed refers to data that is not controlled by the individual who is represented by the authentication token. The key causing the error will be clearly indicated in the error text.
E_invalidValue − A value that was passed in a keyValue attribute did not pass validation. This applies to checked categorizations, identifiers and other validated code lists. The error text will clearly indicate the key and value combination that failed validation.
E_requestTimeout − It signifies that the request could not be carried out because a needed validate_values service did not respond in a reasonable amount of time. Details identifying the failing service will be included in the dispositionReport element.
E_valueNotAllowed − Restrictions have been placed by the taxonomy provider on the types of information that should be included at that location within a specific taxonomy. A validate_values service chosen by the Operator Site has rejected this businessEntity for at least one specified category.
E_accountLimitExceeded − It signifies that user account limits have been exceeded.