Service Registry 3.1 Release Notes

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, then 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 has Side Effect of Deleting ExternalLink

Problem Summary: If versioning is enabled, and if you add a Slot, a Classification, or an 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 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: In the Web Console, 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

6407195: Most Admin Tool Commands Ignore lcd Setting

Problem Summary: If you use the Admin Tool lcd command to set your current local directory, the cp command accepts path name arguments relative to this directory. Most other commands, however, do not do so (add user, import, and keystoreMover, for example). For these commands you need to specify an absolute path name.

6407974: Many Files Left Around in Temporary Directory

Problem Summary: The WSDL cataloging service leaves XML and XSLT files on the server, in the directory specified by the property of the 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 like the following can be deleted. The characters ????? represent a 5–digit number.


6436598: WSDL Cataloger Does Not Delete or Update Cataloged 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; instead, they must be deleted or updated individually. The cataloged objects should be deleted or updated when the service or the WSDL file is deleted or updated.

6479361: FindAllMyObjects Display Should Not Include the Caller's User

Problem Summary: When a user selects and executes the FindAllMyObjects query in the Web Console, the results display includes the User object for the user who executed the query, along with all other objects owned by the user. If the user inadvertently deletes this object, major problems result: the user can no longer perform any actions on objects that he or she published as that user, and he or she must perform user registration again in order to publish more objects. The FindAllMyObjects query should not display this User object. Only the GetCallersUser query should display this object.

Workaround: Be careful not to delete your own User object.

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

Problem Summary: While a user is creating an object of any type in the Web Console, the Set or Change Status button is not grayed out. However, it is not possible to set or change the status of an object that has not yet been created. If the user clicks 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, 6501767: Status of Modified Object is Null

Problem Summary: If you create an object, it has the status Submitted. After you modify it and save it, however, its status changes to null. It should continue to have the status Submitted.

In the Web Console, after you modify the object, the text in the Status pull–down menu changes from Submitted to Select Status (bug 6501767).

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 of the Web Console, the text says to click OK after choosing a concept, but the button is labelled Close.

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 Cataloger Does Not Handle with Trailing Forward Slash

Problem Summary: On the Solaris, HP-UX, and Windows platforms, an attempt to use the WSDL cataloger on a zip file fails if the JVM property 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 cataloger could not find one of the files in the request.

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

Workaround: Change the value of 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 (all on one line):

    On Solaris OS and HP-UX:

    On Windows:\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.

6507387: If Versioning Is Enabled, Attempt to Add Existing Service to Organization Fails

Problem Summary:If you enable versioning and use the JAXR provider to create an Organization object to which you add an existing Service object before saving the Organization, the program fails with a stack trace.

6513883: On HP-UX Systems, User Registration Fails with Internet Explorer 6

Problem Summary: If you perform user registration in the Web Console on an HP-UX system using Internet Explorer 6, you will have problems accessing the generated certificate. Specifically, if you register, download the generated certificate, and then import it into Internet Explorer 6, you may be able to log in to Service Registry once, but subsequent attempts to log in will fail. Assertion failures appear in the server log file.

Workaround: Use a different browser, such as Firefox, to access the Web Console on HP-UX systems.