Direct links to fixes
APAR status
Closed as program error.
Error description
WSDL and XSD documents can be updated via the WSRR API and Eclipse plugin. The problem is that during update WSRR does not use the document's dependencies to resolve other documents, so it is not possible to update documents which depend on other documents. A further problem is that an update always resulted in all logical objects being deleted, even if their corresponding element in the updated document was not changed. Finally if a WSDL document was updated to change the endpoint for a SOAP service (a SOAP Address), then the correlated object SOAP Service Endpoint did not update, and would reflect the old endpoint address. Also it was not possible to update document content from the Business Space user interface. It was not possible to discover which object controlled the governance state of a displayed object in Business Space, which means a user was unable to find which object to transition to alter the governance state of the displayed object.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of WebSphere Service Registry and Repository V8.0 **************************************************************** PROBLEM SUMMARY: Content update will now use the existing document dependencies to resolve dependencies. The update will re-use logical objects when their WSDL or XSD objects have not changed. The SOAP Service Endpoint name will change if a SOAPAddress location is changed. A new dialog has been added to update document content from the business space UI, for WSDL, XSD, Generic and XML documents. The details widget has been enhanced to show which object controls the governance state of the displayed object, providing a link to view details of the controlling object.
Problem conclusion
The changes are targeted for inclusion in WSRR v8.0.0.2
Temporary fix
Comments
APAR Information
APAR number
IV44531
Reported component name
SERVICE REGISTR
Reported component ID
5724N7200
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-06-20
Closed date
2013-06-25
Last modified date
2013-06-25
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
SERVICE REGISTR
Fixed component ID
5724N7200
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSWLGF","label":"WebSphere Service Registry and Repository"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
25 June 2013