| 
| 
| |
Ruddi is divided into a set of packages that each have a specific purpose. This section lists the various Ruddi packages, details their purpose and gives informations on the types of classes they contain.
The "inspireit.uddi" package contains Ruddi classes representing the main UDDI notions such as businessEntity , businessService , bindingTemplate , tModel and publisherAssertion . The name of the Ruddi classes directly correspond to the UDDI notions they represent, i.e. respectively BusinessEntity , BusinessService , BindingTemplate , TModel and PublisherAssertion .
The "inspireit.uddi.base" package contains Ruddi classes representing the entire set of UDDI data structures such as address, contact, etc. The name of the Ruddi classes directly correspond to the UDDI data structures they represent, i.e. respectively Address , Contact , etc.
The "inspireit.uddi.collections" package contains Ruddi collections classes. There is one collection class per UDDI data structure, i.e. there is one collection per class in the "inspireit.uddi.base" package. The name of a collection class for a given Ruddi data structure corresponds to its plural form. I.e, Addresses , Contacts ,..., are respectively Ruddi collection classes for the Address , Contact ,..., Ruddi data structures. When interacting with an UDDI registry, some Ruddi collection instances may be serialized to actual UDDI collections, while others may be serialized against "flat" item lists.
The "inspireit.uddi.collections.iterators" package contains Ruddi iterators for the various Ruddi collections. The name of an iterator class for the collection of a given Ruddi data structure corresponds to the name of the Ruddi data structure followed by "Iterator". For example, the Addresses collection of Address data structures has a corresponding AddressIterator iterator class.
The "inspireit.uddi.io" package contains Ruddi input and output classes. For example, the UDDIInputStream class defines methods allowing reading UDDI registry responses from an InputStream. The UDDI responses are automatically deserialized as high-level Ruddi response objects such as BindingDetail or ServiceInfo .
The "inspireit.uddi.io.serialize" package contains Ruddi classes to serialize Ruddi data structures to UDDI-compliant XML format. Ruddi serializers support UDDI 3.0, 2.0 and 1.0.
The "inspireit.uddi.net" package contains Ruddi networking classes. For example, the RemoteException class represents a communication-related exception that occurred during the execution of an UDDI remote method call.
The "inspireit.uddi.request" package contains Ruddi request classes such as UDDIPublisher , UDDIQuerier and UDDIProfile . UDDIPublisher and UDDIQuerier respectively allow invoking the publishing and inquiry APIs of an UDDI registry, while UDDIProfile allows defining an execution context for an UDDI client/server interaction.
The "inspireit.uddi.request.base" package contains Ruddi classes representing the entire set of UDDI data structures specific to a request execution used when interacting with an UDDI registry, such as findQualifier , completionStatus , etc. The name of the Ruddi request base classes directly correspond to the UDDI request data structures they represent, i.e. respectively FindQualifier , CompletionStatus , etc.
The "inspireit.uddi.response" package contains Ruddi classes representing the entire set of possible UDDI registry replies such as businessDetail , bindingDetail , etc. The name of the Ruddi response classes directly correspond to the UDDI response data structures they represent, i.e. respectively BusinessDetail , BindingDetail , etc.
The "inspireit.uddi.response.base" package contains the Ruddi classes representing the entire set of UDDI data structures specifically used to encapsulate UDDI registry responses such as businessInfo , serviceInfo , result , etc. The name of the Ruddi response base classes directly correspond to the UDDI response data structures they represent, i.e. respectively BusinessInfo , ServiceInfo , Result , etc.
The "inspireit.uddi.util" package contains various Ruddi utility classes to manipulate UDDI keys, for example.
The "inspireit.uddi.util.validators" package contains Ruddi validators allowing validating Ruddi data structures for compliance with restrictions placed by the UDDI specification on the format, length, or other characteristic of an UDDI data structure. The name of a validator class for a given Ruddi data structure corresponds to the name of the Ruddi data structure followed by "Validator". For example, the AddressValidator validates the Address data structure.
| |
(c) INSPIRE IT, 2003 | Send us your feedback: developers@ruddi.biz