test

Service Registry 3.1 Release Notes for Microsoft Windows

Known Issues and Bugs

The following known issues and bugs affect the operation of the Service Registry 3.1 release.

6248218: Versioned RegistryPackage Loses Its Contents

Problem Summary: If versioning is enabled and if you change a RegistryPackage object so as to create a new version of the object, all the package contents disappear from the new version.

Workaround: Do not enable versioning. See Enabling Versioning of Registry Objects in Service Registry 3.1 Administration Guide for more information.

6248293: Classification Is Added to Both Old and New Versions of Object

Problem Summary: If versioning is enabled, and if you add a classification to one version of the object and save the object, the classification now exists in both the old version and the new version.

Workaround: Do not enable versioning. See Enabling Versioning of Registry Objects in Service Registry 3.1 Administration Guide for more information.

6248418: Adding Classification, ExternalIdentifier, or Slot Deletes ExternalLink

Problem Summary: If versioning is enabled, and if you add a Slot, Classification, or ExternalIdentifier to an object that has an ExternalLink, the ExternalLink disappears from the new version of the object.

Workaround: Do not enable versioning. See Enabling Versioning of Registry Objects in Service Registry 3.1 Administration Guide for more information.

6359188: Attempt to Create Association To or From a Deprecated Object Owned by User Does Not Cause IllegalStateException

Problem Summary: The JAXR specification does not allow a user to create an association either to or from an object that is deprecated. However, the Service Registry JAXR provider permits a user to create such an association if the user owns the deprecated object.

6374079: Person and User Details Areas Aren't Identical

Problem Summary: The Details area for a Person object does not allow the user to add a PostalAddress, EmailAddress, or TelephoneNumber, although a Person object contains all those attributes.

Workaround: Create a User object instead of a Person object. You can add all these attributes to a User object.

6407168: Admin Tool add association Command Outputs Misleading Errors

Problem Summary: An attempt to issue the Admin Tool command add association to create an association that the user is not authorized to perform results in a misleading error message. For example, if a user who is not an administrator tries to create an association of type HasMember, the following error message appears:

No Concept object exists for type: HasMember

6407974: Many Files Remain in Temporary Directory

Problem Summary: The WSDL cataloguing service leaves XML and XSLT files on the server, in the directory specified by the java.io.tmpdir property of the install.properties file. In addition, the user authentication process leaves files that begin with .omar and have the suffix .jks in the same directory. These files are not deleted until the Registry domain is stopped.

Workaround: Files with names similar to the following examples can be deleted. The n variable represent a number.

CanonicalXMLValidationService_OutputFilennnnn.xml
InvocationControlFile_WSDLValidationnnnnn.xslt

6422192: NullPointerException When Using Service Registry 3.1 Admin Tool With Service Registry 3.0

Problem Summary: If you use the Service Registry 3.1 Admin Tool with a deployed Service Registry 3.0 version commands such as cp and rm result in a NullPointerException.

Workaround: Use the Service Registry 3.1 Admin Tool only with Service Registry 3.1, and use the Service Registry 3.0 Admin Tool with Service Registry 3.0.

6436598: WSDL Cataloguer Does Not Delete or Update Catalogued Objects When Source Object Is Deleted or Updated

Problem Summary: When you use the WSDL cataloging service to create a service by publishing a WSDL file to the Registry, the Registry creates a large number of objects that are part of the service. When you delete or update the service or the WSDL file, these objects are not deleted or updated. You must delete or update these objects individuallywhen the service or the WSDL file is deleted or updated.

Workaround: None.

6487653: Set or Change Status Button on Object Creation Does Not Work

Problem Summary: While you create an object, the Set or Change Status button is not dimmed. However, you cannot set or change the status of an object that has not yet been created. If you click this button, an error message appears, stating that the object cannot be found.

Workaround: Do not click the Set or Change Status button on an object that you are creating. Click Apply to complete the creation of the object, then search for the object and change its status.

6499274: Status of Modified Object Is Null

Problem Summary: New objects have the the status Submitted. After you modify and save the object, however, its status changes to null. The object should continue to have the status Submitted.

Workaround: None.

6500654: Description and Button in Select Classification Node Window Do Not Match

Problem Summary: If you click the Select Classification Node button in the Search area, the text says to click OK after choosing a concept, but the button is labelled Close.

Workaround: None.

6500668: User Registration Wizard Does Not Explain Meaning of Asterisk

Problem Summary: In the Web Console, the New User's Details form and the User Authentication Details form contain asterisks, but the forms do not explain that an asterisk indicates a required field.

Workaround: The online help states which fields are required.

6502100: WSDL Cataloguer Does Not Handle java.io.tmpdir With Trailing Forward Slash

Problem Summary: An attempt to use the WSDL cataloguer on a zip file fails if the JVM property java.io.tmpdir is set to a value that ends with a forward slash (/). The symptom of the failure is a CatalogingException with a message that states that the cataloguer could not find one of the files in the request.

This problem does not occur on Linux, where the default setting of java.io.tmpdir does not end with a forward slash.

Workaround: Change the value of java.io.tmpdir so that it does not end with a forward slash.

    Perform the following steps:

  1. Log in to the Application Server Admin Console as described in To Use the Application Server Admin Console in Service Registry 3.1 Administration Guide.

  2. Expand the Configurations node.

  3. Expand the server node, server-config (Admin Config).

  4. Click JVM Settings.

  5. Click the JVM Options tab.

  6. Click Add JVM Option.

  7. In the text field, type the following:

    -Djava.io.tmpdir=c:\DOCUME~1\ADMINI~1\LOCALS~1\Temp

  8. Click Save.

  9. Follow the instructions in To Stop and Restart the Application Server Domain for the Registry in Service Registry 3.1 Administration Guide.

After performing these steps, you should be able to publish a zip file that contains multiple WSDL files.