LI78612: WSDL PARSING ERROR WHEN LOADING A WSDL FILE INTO API MANAGEMENT

APAR status

• Closed as program error.

Error description

• When implementing a REST API and defining a WebService Invoke
  operation, the user may experience a WSDL parsing error when
  
  For example:
  "An error occurred while parsing the WSDL. Invalid FileName
  value: Localname not a valid Name in ''"
  
  The cmc.out file contained this error:
  org.apache.xmlbeans.XmlException: error: Invalid FileName value:
  Localname not a valid Name in ''
  at
  org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile
  (SchemaTypeSystemCompiler.java:225)
  at sun.reflect.GeneratedMethodAccessor910.invoke(Unknown Source)
  at
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
  AccessorImpl.java:56)
  at java.lang.reflect.Method.invoke(Method.java:620)
  at
  org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667)
  at org.apache.xmlbeans.XmlBeans.compileXsd(XmlBeans.java:553)
  at
  com.approuter.studio.wsdl.node.WSDLManagedObject.createSchemaTyp
  eSystem(WSDLManagedObject.java:405)
  

Local fix

• WSDL message binding style was changed to 'document'.
  

Problem summary

• When implementing a REST API and defining a WebService Invoke
  operation, the user may experience a WSDL parsing error when
  
  For example:
  "An error occurred while parsing the WSDL. Invalid FileName
  value: Localname not a valid Name in ''"
  
  The cmc.out file contained this error:
  org.apache.xmlbeans.XmlException: error: Invalid FileName value:
  Localname not a valid Name in ''
  at
  org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile
  (SchemaTypeSystemCompiler.java:225)
  at sun.reflect.GeneratedMethodAccessor910.invoke(Unknown Source)
  at
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
  AccessorImpl.java:56)
  at java.lang.reflect.Method.invoke(Method.java:620)
  at
  org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667)
  at org.apache.xmlbeans.XmlBeans.compileXsd(XmlBeans.java:553)
  at
  com.approuter.studio.wsdl.node.WSDLManagedObject.createSchemaTyp
  eSystem(WSDLManagedObject.java:405)
  
  The problem was occurring because the API Management code was
  incorrectly parsing the WSDL.
  The wsdl style was getting picked from binding instead of
  binding-operation.
  
  The API Management code has been updated to correct this.
  

Problem conclusion

• The fix is targeted for inclusion in IBM API Management V4.0.1.0
  
  IBM API Management Announcements can be found on the Support
  Portal at
  http://www-947.ibm.com/support/entry/portal/overview/software/we
  bsphere/ibm_api_management
  

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

  IBM API MANAGEM

• Fixed component ID

  5725L3000

Applicable component levels