- You attempt to run UDDI Utility Tools, but you get the following
error:
java.lang.noClassDefFoundError: com/ibm/uddi/promoter/CommandLineProcessor
- Ensure that you have edited the supplied properties file, UDDIUtilityTools.properties and
that the file contains appropriate values for your environment. For
details of the files that are required on the classpath, and an example
properties file, see the topics about UDDI Utility Tools prerequisites
and the UDDI Utility Tools configuration file.
- Ensure that you use the level of Java code that is supplied with
WebSphere Application Server.
- PublisherAssertions are not supported and are not promoted.
To
resolve this issue, after you promote the businesses that are related,
recreate the publisherAssertion relationship.
- Referenced businesses in service projections are not added automatically
to the entity definition file in the same manner as referenced tModel
entities.
To resolve this issue, add the referenced business that
owns the projected service to the entity definition file. If the business
is not present in the target registry, place it before the owning
business of the service in the entity definition file.
- Cycle detection for service projections are not detected in the
same manner as for referenced tModel entities.
To resolve this issue,
if a circular reference is present between two or more service projections,
break the cycle by removing one of the projections temporarily, perform
the import, and update the changed entity to establish the cycle again
in the target registry.
- The tModel entities that are deleted, in the logical sense, in
the source registry are imported and promoted as undeleted in the
target registry. This is because, in the UDDI Version 2 specification,
the deleted state of tModel entities is not exposed as API calls.
To
resolve this issue, after importing the tModel entity, perform a delete,
using the UDDI Utility Tools delete function, or any other UDDI registry
API access method.
- BindingTemplates that are referenced by hostingRedirectors are
not added automatically to the entity definition file in the same
manner as referenced tModel entities.
To resolve this issue, add
the referenced bindingTemplate to the entity definition file.
- Businesses that are referenced by an owningBusiness keyedReference
are not added automatically to the entity definition file.
To resolve
this issue, import the referenced business into the target registry
before importing the tModel that references it.
- With an embedded Apache Derby database, the import and promote
functions are not supported when referencing a target registry.
To
resolve this issue, make the embedded Apache Derby database network-enabled.
For information about configuring network Apache Derby, refer to the
section about managing the Derby Network Server in the Derby Server and Administration Guide.
The
export and delete functions when referencing a source registry with
an embedded Apache Derby database are supported.
- Some combinations of command-line arguments are not validated
and prevented. For example, it is possible to specify -import with -keysFile path_to_file in
the same command, although the -keysFile option
is ignored.