pax_global_header 0000666 0000000 0000000 00000000064 11736671340 0014522 g ustar 00root root 0000000 0000000 52 comment=8ef8a090d2870a1bc475baad81071b553a4433f9
uddi4j-2.0.5/ 0000775 0000000 0000000 00000000000 11736671340 0012711 5 ustar 00root root 0000000 0000000 uddi4j-2.0.5/BuildDate.txt 0000664 0000000 0000000 00000000051 11736671340 0015303 0 ustar 00root root 0000000 0000000 UDDI4J OpenSource BuildDate : 27-Jun-2006 uddi4j-2.0.5/LICENSE.html 0000664 0000000 0000000 00000034453 11736671340 0014672 0 ustar 00root root 0000000 0000000
IBM Public License Version 1.0
THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS IBM PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.
1. DEFINITIONS "Contribution" means:
"Contributor" means IBM and any other entity that distributes the Program.
"Licensed Patents " mean patent claims licensable by a Contributor which are necessarily infringed by the use or sale of its Contribution alone or when combined with the Program.
"Original Program" means the original version of the software accompanying this Agreement as released by IBM, including source code, object code and documentation, if any.
"Program" means the Original Program and Contributions.
"Recipient" means anyone who receives the Program under this Agreement, including all Contributors.
2. GRANT OF RIGHTS
3. REQUIREMENTS A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that:
When the Program is made available in source code form:
Each Contributor must include the following in a conspicuous location in the Program:
In addition, each Contributor must identify itself as the originator of its Contribution, if any, in a manner that reasonably allows subsequent Recipients to identify the originator of the Contribution.
4. COMMERCIAL DISTRIBUTION Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like. While this license is intended to facilitate the commercial use of the Program, the Contributor who includes the Program in a commercial product offering should do so in a manner which does not create potential liability for other Contributors. Therefore, if a Contributor includes the Program in a commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a commercial product offering. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Contributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations. The Indemnified Contributor may participate in any such claim at its own expense.
For example, a Contributor might include the Program in a commercial product offering, Product X. That Contributor is then a Commercial Contributor. If that Commercial Contributor then makes performance claims, or offers warranties related to Product X, those performance claims and warranties are such Commercial Contributor's responsibility alone. Under this section, the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages.
5. NO WARRANTY EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations.
6. DISCLAIMER OF LIABILITY EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
7. GENERAL If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this Agreement, and without further action by the parties hereto, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.
If Recipient institutes patent litigation against a Contributor with respect to a patent applicable to software (including a cross-claim or counterclaim in a lawsuit), then any patent licenses granted by that Contributor to such Recipient under this Agreement shall terminate as of the date such litigation is filed. In addition, If Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient's patent(s), then such Recipient's rights granted under Section 2(b) shall terminate as of the date such litigation is filed.
All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware of such noncompliance. If all Recipient's rights under this Agreement terminate, Recipient agrees to cease use and distribution of the Program as soon as reasonably practicable. However, Recipient's obligations under this Agreement and any licenses granted by Recipient relating to the Program shall continue and survive.
IBM may publish new versions (including revisions) of this Agreement from time to time. Each new version of the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to distribute the Program (including its Contributions) under the new version. No one other than IBM has the right to modify this Agreement. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to the intellectual property of any Contributor under this Agreement, whether expressly, by implication, estoppel or otherwise. All rights in the Program not expressly granted under this Agreement are reserved.
This Agreement is governed by the laws of the State of New York and the intellectual property laws of the United States of America. No party to this Agreement will bring a legal action under this Agreement more than one year after the cause of action arose. Each party waives its rights to a jury trial in any resulting litigation. |
UDDI4J releases can be downloaded from SourceForge.
Release name | Date | Notes |
2.0.5 | 06/27/2006 | UDDI4J minor update release containing minor bug fixes - see Change Log below. |
2.0.4 | 10/31/2005 | UDDI4J minor update release containing minor bug fixes - see Change Log below. |
2.0.3 | 03/22/2005 | UDDI4J minor update release containing minor bug fixes - see Change Log below.
The binary distribution for this release does not contain the compiled class file for HPSOAPTransport. Users wishing to use HPSOAPTransport must download the source distribution and compile this class themselves using the supplied build.xml file. |
2.0.2 | 09/04/2003 | UDDI4J minor update release containing minor bug fixes. |
2.0.1 | 01/30/2003 | UDDI4J minor update release, including updated Axis support, spec compliance fixes, and minor bug fixes. |
2.0 | 5/15/2002 | UDDI4J release with v2 support. Minor changes from 2.0 beta. Errata 3 support, bug fixes, collection class enhancements. |
2.0 beta | 11/09/2001 | Major new release support UDDI v2 specification. Collaboration with HP. |
1.0.3 | 06/26/2001 | Important bug fix corrects problem with multiple 'name' attributes being misinterpreted |
1.0.2 | 03/28/2001 | bug fixes |
1.0.1 | 02/16/2001 | bug fixes |
1.0 | 01/24/2001 | UDDI4J contributed by IBM to open source community on Developerworks |
1.0 beta | 11/13/2000 | Initial release as part of Web Services Toolkit v2.0 available on Alphaworks |
Changes from 2.0.4 release include:
- Fix DBCS problem in ApacheAxisTransport, causing DBCS characters to be translated incorrectly.
Changes from 2.0.3 release include:
- Introduction of more flexible properties handling including ability to specify configuration properties in a uddi4j.properties file.
- UDDI4J is now XML namespace aware
Changes from 2.0.2 release include:
- UDDIElement now implements Serializable (and hence so do all the datatype classes which are subclasses of UDDIElement).
- ApacheAxisTransport updated to work with Crimson parser as well as Xerces.
- ApacheSOAPTransport now catches generic Exception rather than SOAPException from calls into Apache SOAP.
This prevents RuntimeExceptions from Apache SOAP propagating through UDDI4J.- Organized imports to aid compilation.
- Corrected some javadoc errors.
Important information for release 2.0.3:
- The binary distribution of the 2.0.3 release does not contain the compiled class file for HPSOAPTransport. (The source distribution still contains the source file for this class.) This will not affect users of ApacheSOAPTransport (the default) or ApacheAxisTransport. Users wishing to use the HPSOAPTransport class will need to download the source distribution and build UDDI4J themselves using the supplied build.xml file.
Changes from 2.0.1 release include:
- Miscellaneous bug fixes.
Changes from 2.0 release include:
- Axis 1.x update
- Ant 1.5.x update
- BindingTemplate
Required fields constructors updated to ensure either HostingRedirector or AccessPoint is present.- BusinessInfo
Updated to support multiple Name objects.- DispositionReport
Updated to include missing 'truncated' attribute.
Updated to better represent the component objects of a DispositionReport.- KeysOwned
Minor fixes to avoid Null Pointer Exceptions.- RelatedBusinessInfo
Updated to support multiple Name and Description objects.- ServiceInfo
Updated to support multiple Name objects.- TModelInfo
Minor fix to avoid possible Null Pointer Exception.- 'All Publish API requests'
Minor updates to avoid possible Null Pointer Exception.- FindService, FindBusiness, FindTModel, GetCompletionStatus, AuthToken
Minor updates to avoid possible Null Pointer Exception.- BindingDetail, BusinessDetail, BusinessDetailExt, BusinessList, ServiceList, TModelDetail, TModelList
Updated to avoid Null Pointer Exception handling optional truncated attribute.
Changes from 2.0 beta include:
- Support for UDDI V2 errata 3
- Configuration object to override system property settings in UDDIProxy.
- Collection class methods added to classes that are primarily collections.
- Addressline class added support for keyname, keyvalue.
- Other miscellaneous bug fixes and enhancements.
Major revision. New capabilities include:
- Full support of the UDDI V2 specification
- Support for plugable SOAP transports. Currently the supported SOAP implementations include
- Apache SOAP 2.2 (http://xml.apache.org/soap/)
- HP SOAP (http://www.hp.com/go/webservices)
- Axis (http://xml.apache.org/axis/)
- Logging capability
- Improved configuration capability
Other major changes:
- Package name changed to org.uddi4j
- UDDI v1 messages are no longer supported.
Major contribution by HP to the project as they join the development community.
This release contains a significant bug fix. Users of previous releases are strongly encouraged to upgrade.
Corrected problem incorrecting interpreting 'name' attributes contained at multiple levels when invoking save requests.
The getDescriptionStrings methods have been removed from all classes that had them. They have been replaced with getDefaultDesriptionString method.
The getDescriptionStrings method was misleading. Each string in the returned vector represented a different language, yet there was no way to figure out what language each string was for. getDefaultDescriptionString returns the default (english) string.
To obtain all the descriptions, use the getDescriptionVector method. This returns Description objects which contain a language attribute.
Some fixes have been checked in to required field constructs that accepted Vectors of Strings. This does not affect their signatures. Affected classes are: DeleteBinding, DeleteBusiness, DeleteService, DeleteTModel, GetBindingDetail, GetBusinessDetail, GetBusinessDetailExt, GetServiceDetail, GetTModelDetail, TModelBag.
Required fields constructors corrected for some objects.
Samples added to source distribution.
Initial submission by IBM of UDDI4J to open source community on Developerworks.
Included as part of IBM Web Services Toolkit version 2.0 available on Alphaworks.uddi4j-2.0.5/build.xml 0000664 0000000 0000000 00000027752 11736671340 0014547 0 ustar 00root root 0000000 0000000
The UDDI (Universal Description, Discovery and Integration) Project is a comprehensive, open industry initiative enabling businesses to (I) discover each other, and (II) define how they interact over the internet and share information in a global registry architecture. UDDI is the building block which will enable businesses to quickly, easily and dynamically find and transact with one another via their preferred applications.
UDDI4J is a Java class library that provides an API that is can be used to interact with a UDDI registry. This class library generates and parses messages sent to and received from a UDDI server.
The central class in this set of APIs is org.uddi4j.client.UDDIProxy. It is a proxy for the UDDI server that is accessed from client code. Its methods map to the UDDI Version 2.0 API Specification.
The classes within org.uddi4j.datatype represent data objects used to send or receive UDDI information. and in the, business, service, tmodel subpackages represent data objects that are sent on calls or received from the server.
The subpackage org.uddi4j.request contains messages sent to the server. These classes are typically not used directly, rather the UDDIProxy class uses these classes.
Similarly, the subpackage org.uddi4j.response represents response messages from a UDDI
server.
Pluggable transports are supported by the package org.uddi4j.transport.
UDDIException is thrown when errors are received from the UDDI proxy when invoking UDDIProxy inquiry methods. UDDIException can contain a DispositionReport with information about the error.
APIs that do not return a data object return a disposition report directly.
TransportException is thrown if a communication error occurs or if the resulting data cannot be properly parsed as a valid SOAP message. This new exception class is required since the previous use of SOAPException created a dependency on Apache SOAP. TransportException wrappers any communications exception thrown by the underlying SOAP transport implementation (Axis, SOAP, HP-SOAP). The native exception is available, and a stack trace will indicate where the TransportException was thrown as well as the native exceptions stack trace.
UDDI4J uses a variety of properties to configure behavior. These properties may be set in a variety of ways.
The order of precedent for each method is as follows with the highest precedence first.
java.util.Properties
object passed to UDDIProxy(Properties) constructorProperty name | Values | Description |
---|---|---|
org.uddi4j.TransportClassName | org.uddi4j.transport.ApacheSOAPTransport,
org.uddi4j.transport.HPSOAPTransport,
org.uddi4j.transport.ApacheAxisTransport. If missing, it defaults to org.uddi4j.transport.ApacheSOAPTransport. The property will be read at startup time, and any change at run time (after the TransportFactory has been invoked) will not have any effect. |
Selecting a SOAP transport |
org.uddi4j.logEnabled | true or false. If missing, it defaults to false. The property can be changed at run time, and will be checked each time a UDDI message is sent out. Turning logging on or off. |
Turning logging on or off. |
http.proxyHost | Valid host name. | Hostname of http proxy |
https.proxyHost | Valid host name. Defaults to hostname of http proxy. | Hostname of https proxy |
http.proxyPort | Valid port number. Defaults to 80. | Port of http proxy. |
https.proxyPort | Valid port number. Defaults to http.proxyPort. | Port of https proxy. |
http.proxyUserName | Valid user name. | Username for proxy server |
http.proxyPassword | Valid password | Password for proxy server |
http.basicAuthUserName | Valid user name. | Username to use with HTTP Basic Authentication |
http.basicAuthPassword | Valid password | Password to use with HTTP Basic Authentication |
Property name | Allowed Values/Default behavior | Description |
---|---|---|
hpsoap.logDirectory | Valid directory path. In case it is null/missing, or invalid or any error while accessing this directory, the log file will be created in the current directory. The property will be read at startup time, and any change at run time (after the TransportFactory has been invoked) will not have any effect. |
Directory path of log file |
hpsoap.logFileName | Valid file name. In case it is missing, logging will be turned off. In case it is present, but null valued, all logging information will be sent to System.err If file open/write fails, all log information is sent to System.err. The property will be read at startup time, and any change at run time (after the TransportFactory has been invoked) will not have any effect |
File name of log file |
Please note that the HP-SOAP transport will only read System properties and will ignore properties passed to the UDDIProxy(Properties) constructor or set in a uddi4j.properties file.
The user can set these properties at startup
time
C:> java Dorg.uddi4j.TransportClassName=org.uddi4j.transport.HPSOAPTransport
-Dorg.uddi4j.logEnabled=true SomeUDDIClient
The user can set these properties at run
time
System.setProperty (hpsoap.logDirectory,/tmp);
System.setProperty (hpsoap.logFileName,uddi4j.log);
System.setProperty (org.uddi4j.logEnabled,true);
UDDIProxy uddiProxy = new UDDIProxy ();
To run a program referencing UDDI4J,
ant targetwhere target is one of the following:
A set of samples is provided to illustrate the basics of using the inquiry api, publish api, and error handling.
The samples require several pieces of information including the following:
A property file is used by the samples to
read values that may need to be modified.
This property file includes the values listed
above, as well as a convenient way to set
the system properties used by UDDI4J as described
in Configuration.
To run the examples, set the classpath as described above, invoke java or jre with the desired sample program name. Example:
java FindBusinessExample
IBM is a registered trademark of IBM,
HP is a registered trademark of Hewlett-Packard Company
Copyright© IBM Corporation 2001, All rights reserved.