Home >> All >> org >> apache >> [ juddi Javadoc ]

Page 1   2  

•	org.apache.juddi.transport.* (5)	•	org.apache.juddi.util.* (9)	•	org.apache.juddi.uuidgen.* (6)
•	org.apache.juddi.validator.* (3)

• org.apache.juddi: Javadoc index of package org.apache.juddi.


Package Samples:

• org.apache.juddi.transport.axis
• org.apache.juddi.util.jdbc
• org.apache.juddi.util.xml
• org.apache.juddi.util
• org.apache.juddi.uuidgen
• org.apache.juddi.validator

Classes:

• ValidateValues: "Whenever save_business, save_service or save_tModel are called, the contents of any included categoryBag or identifierBag element may be checked to see that it contains valid values. Checking is performed for taxonomies and identifier schemes that are classified as "checked". UDDI version 2 provides the ability for third parties to register new taxonomies and identifier schemes, and then control the validation process used by UDDI to perform such checks. Third parties that want to provision such a capability must implement a web service in the same manner that UDDI does (e.g. using SOAP 1.1 over ...
• TModel: "Descriptions of specifications for services or taxonomies. Basis for technical fingerprints" - XML Structure Reference The primary role that the tModel plays is to represent a technical spec. Implementors of that spec reference the tModel with a tModelKey in a bindingTemplate in the service definition. The other place that a tModel reference is used is in the identifierBag and categoryBag structures. Used in this context the tModel reference represents a relationship between the keyed name-value pairs to the namespace within which they are meaningful. Eg, a tModel named "US tax codes". The tModel ...
• SubscriptionResultsList: Example: 20020727T00:00:00 20020728T00:00:00 BindingKey of the subscribers NotifySubscriptionListener service P1D 1000 20030101T00:00:00 false uddi:BeerSupplies.com:maltSelectionService uddi:Containers.com:kegs:orderingService
• FindBusinessFunction: "This [FindBusiness] API call returns a businessList on success. This structure contains information about each matching business, and summaries of the businessServices exposed by the individual businesses. If a tModelBag was used in the search, the resulting serviceInfos structure will only reflect data for the businessServices that actually contained a matching bindingTemplate. In the event that no matches were located for the specified criteria, a businessList structure with zero businessInfo structures is returned. If no arguments are passed, a zero-match result set will be returned." "In the ...
• AccessPoint: Is an attribute-qualified pointer to a service entry point. Many types of entry point are accommodated. A single urlType attribute is used to indicate the type of entry point so searches for specific types can be performed. Types might be "http", "smtp", "ftp", etc. In addition there is the actual string value for the entry point. Example accessPoints therefore may be: mailto:purch@fabrikam.com http://www.sviens.com/purchasing ftp://ftp.sviens.com/public, etc. If the AccessPoint has a custom addressformat, the "other" urlType has to be used. When this value is used, one or more of the tModel signatures ...
• Subscription: Example: BindingKey of the subscribers NotifySubscriptionListener service P1D 1000 20030101T00:00:00
• FindPublisherFunction: "This [FindPublisher] API call returns a publisherList on success. This structure contains information about each matching publisher. In the event that no matches were located for the specified criteria, a publisherList structure with zero publisher structures is returned. If no arguments are passed, a zero-match result set will be returned." In the event of a large number of matches, (as determined by each Operator Site), or if the number of matches exceeds the value of the 'maxRows' attribute, the Operator Site will truncate the result set. If this occurs, the publisherList will contain the 'truncated' ...
• PublisherAssertion: Many businesses, like large enterprises or marketplaces, are not effectively represented by a single businessEntity, since their description and discovery are likely to be diverse. As a consequence, serveral BusinessEntity structures can be published, representing individual subsidiaries of a large enterprise or individual participants of a marketplace. Nevertheless, they still represent a more or less coupled community and would like to make some of their relationships visible in their UDDI registrations. Therefore two related businesses use the xx_pulisherAssertion messages, publishing assertiions ...
• XMLDocAuthenticator: This is a simple implementation of jUDDI's Authenticator interface. The credential store is simply an unencrypted xml document called 'juddi.users' that can be found in jUDDI's config directory. Below is an example of what you might find in this document. Example juddi.users document: =============================
• BindingTemplate: Technical web service description. Contains "information relevant for application programs that need to connect to and then communicate with a remote Web Service. This information includes the address to make contact with a Web Service, as well as support for option information that can be used to describe both hosted services and services that require additional values to be discovered prior to invoking a service" - technical whitepaper "Technical information about a service entry point and construction specs" - XML Structure Reference
• GetAssertionStatusReport: "The get_assertionStatusReport API call provides administrative support for determining the status of current and outstanding publisher assertions that involve any of the business registrations managed by the individual publisher account. Using this message, a publisher can see the status of assertions that they have made, as well as see assertions that others have made that involve businessEntity structures controlled by the calling publisher account. See Appendix J on relationships and publisher assertions for more information."
• DiscoveryURL: A businessEntity has a "discoveryURLs" attribute which is a collection of these. Consists of an attribute whose value designates the URL use type convention and a string found within the body of the element. The use type will be "businessEntity" or "businessEntityExt" according to the containing object being saved. Each time a businessEntity object is saved this collection is augmented with the new URL identifying the newly saved object. The useType can be an empty string ("") if the discoveryURL is used in a find_business message.
• FindServiceByTModelKeyQuery: tModelBag: This is a list of tModel uuid_key values that represent the technical fingerprint of a bindingTemplate structure to find. All bindingTemplate structures within any businessService associated with the businessEntity specified by the businessKey argument will be searched. If more than one tModel key is specified in this structure, only businessService structures that contain bindingTemplate structures with fingerprint information that matches all of the tModel keys specified will be returned (logical AND only).
• TestFindServiceByTModelKeyQuery: tModelBag: This is a list of tModel uuid_key values that represent the technical fingerprint of a bindingTemplate structure to find. All bindingTemplate structures within any businessService associated with the businessEntity specified by the businessKey argument will be searched. If more than one tModel key is specified in this structure, only businessService structures that contain bindingTemplate structures with fingerprint information that matches all of the tModel keys specified will be returned (logical AND only).
• TModelInstanceInfo: A TModelInstanceInfo object represents the BindingTemplate instance specific details for a single TModel by reference. A set of these is held by the TModelInstanceDetails Map. When taken as a group they form a technically descriptive fingerprint by virtue of the unordered list of tModelKey references that they form. Each singular TModelInstanceInfo refers to a single tModel, and its presence in a bindingTemplate.tModelInstanceDetails implies that this containing web service supports the tModel that is referenced.
• HostingRedirector: The HostingRedirector in the bindingTemplate is used to indicate that the bindingTemplate entry is a pointer to a different bindingTemplate entry. The value in this is seen when a business or entity wants to expose a service description (ie advertise a service that fulfills a specific purpose) that is actually a service that is described in a separate bindingTemplate record. This might occur when a service is remotely hosted or when many service descriptions could benefit from a single service description.
• FindQualifiers: "Knows about the creation and populating of FindQualifiers objects. Returns FindQualifiers." Example Usage: // build the find qualifiers instance FindQualifiers qualifiers = new FindQualifiers(); qualifiers.add(new FindQualifier(FindQualifier.exactNameMatch)); qualifiers.add(new FindQualifier(FindQualifier.andAllKeys)); // set find qualifiers into request FindBusiness findBusiness = new FindBusiness(); findBusiness.setFindQualifiers(qualifiers);
• Address: Represents a postal address. Essentially holds a simple set of AddressLines, but can be adorned with an optional useType attribute and sortcode. The useType attribute is used to describe the type of the address in freeform text. Examples are "headquarters", "billing department", etc. The sortCode values are not significant, but can be used by user-interfaces that present contact information in some ordered fashion, thereby using the sortCode values.
• ServiceDetail: "This structure contains full details for zero or more businessService structures. It is returned in response to a get_serviceDetail message, and optionally in response to the save_binding and save_service messages." "Note that the businessKey value is supplied in this message because the container does not provide a link to the parent businessEntity structure" XML Structure Reference. (The businessKey in the businessService must be populated).
• BusinessList: "This structure contains abbreviated information about registered businessEntity information. This message contains zero or more businessInfo structures. It is returned in response to a find_business message." "BusinessInfo structures are abbreviated versions of BusinessEntity data suitable for populating lists of search results in anticipation of further drill-down detail inquiries." - XML Structure Reference
• JBossAuthenticator: This is a implementation of jUDDI's Authenticator interface, that uses the JBoss authentication manager. Usage: To use this class you must add the following properties to the juddi.properties file: # The JBoss Authenticator juddi.auth=org.apache.juddi.auth.JBossAuthenticator # The security-domain, defined in $JBOSS/default/conf/login-config.xml juddi.securityDomain=java:/jaas/other
• Description: A Description object contains a textual description and an optional language code. A default ISO language code will be determined for a publisher at the time that a party establishes permissions to publish at a given operator site or implementation. This default language code will be applied to any description values that are provided with no language code.
• UUIDGen: A Universally Unique Identifier (UUID) is a 128 bit number generated according to an algorithm that is garanteed to be unique in time and space from all other UUIDs. It consists of an IEEE 802 Internet Address and various time stamps to ensure uniqueness. For a complete specification, see ftp://ietf.org/internet-drafts/draft-leach-uuids-guids-01.txt [leach].
• TModelList: "This structure contains abbreviated information about registered tModel information. This message contains zero or more tModelInfo structures. It is returned in response to a find_tModel message." "This data is suitable for finding candidate tModels, populating lists of results, and then providing drill-down features that rely on the get_xxDetail messages.
• FunctionMaker: Holds a static HashMap linking the string representation of operations to instantances of the appropriate maker class (BusinessDetail to BusinessDetailHandler). Returns a reference to an instance of a maker object. HandlerMaker follows the Singleton pattern (GoF p.127). Use getInstance instead of the 'new' operator to get an instance of this class.

Home | Contact Us | Privacy Policy | Terms of Service