PK44710: WSDL validator with WS-I enabled does not flag if SOAP 1.2 names pace binding is used

Rational Application Developer for WebSphere Software, Version 7.0.0.6
Rational Software Architect, Version 7.0.0.6

APAR status

• Closed as program error.

Error description

• WSDL validator with WS-I enabled does not flag if SOAP 1.2 names
  pace binding is used
  1.Version (with iFixes and TestFixes).
  RAD v6.0.1.1 + Ifix004 target WAS60
  same for RAD7
  2.Problem Description.
  Customer could not generate web service client  form a WSDL usin
  g SOAP 1.2 namespace bindings not supported by WAS v6.x
  WSDL validator did not flag thisfro WS-I compliance
  Workaround:
  change the namespace his bindings
  from SOAP 1.2 to SOAP ( == 1.1)
  Example change
  the namespace line:
  xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/
  and change it to show just soap:
  xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap/
  

Local fix

Problem summary

• The RAD 7 WSDL validator with WS-I profile compliance
  enabled does not flag if SOAP 1.2 namespace binding is used.
  

Problem conclusion

• According to the WS-I Basic profile, the restriction to use
  SOAP 1.1 applies only to conforming bindings and does not
  preclude the WSDL document from containing non-conforming
  bindings.
  
  Accordingly, the Rational Application Developer V7.0.0.6
  WS-I WSDL validator has been improved to produce a problem
  marker when a service does not have at least one SOAP 1.1
  binding.
  
  The marker is attached to a service and it is worded like
  this: "The service does not reference any wsdl:binding
  element that uses a SOAP 1.1 binding".
  

Temporary fix

Comments

APAR Information

• 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

  APP DEV V6 WIN

• Fixed component ID

  5724J1901

Applicable component levels

• R601 PSN

     UP