- 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 - find_service
The find_service function searches for services associated with a specified business.
The response includes a root serviceList element, and one serviceInfo element for each matching company. If the UDDI operator returns only a partial list of matching results, the serviceList element's truncated attribute will be set to true. If no matches are found, a serviceList element with zero sub elements is returned.
Version 2.0 Syntax
<find_service businessKey = "uuid_key" generic = "2.0" [maxRows = "nn"] xmlns = "urn:uddi-org:api_v2"> [<findQualifiers/>] [<name/> [<name/>]...] [<categoryBag/>] [<tModelBag/>] </find_service>
businessKey − Required uuid_key attribute specifying the associated businessEntity.
maxRows − Optional attribute to specify the maximum number of rows to be returned. If maxRows is exceeded, the serviceList element's truncated attribute will be set to true.
findQualifiers − Optional element to override the default search functionality. For example, the find qualifier exactNameMatch will match exact business names.
name − The full or partial name of the service. UDDI 2.0 allows you to specify up to five service names.
categoryBag − Optional element to search by category. If more than one category is specified, the search is performed via a logical AND.
tModelBag − Optional element to search by tModels. If more than one tModel is specified, the search is performed via a logical AND.
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 − It signifies that the uuid_key value passed did not match with any known serviceKey or tModelKey values. The error structure will signify which condition occurred first, and the invalid key will be indicated clearly in text.
E_tooManyOptions − Too many search options were specified.
E_unsupported − The specified findQualifier is not supported.