IT35760: XSDS IN STATIC LIBRARIES REFERENCED IN AN INTEGRATION SERVICE WSDL DOCUMENT ARE NOT REWRITTEN CORRECTLY

APAR status

• Closed as program error.

Error description

• If an XSD in a static library is referenced in the Integration
  Service description, for example as a request or response type
  for an operation, an <xsd:import> or <xsd:include> element is
  added to the WSDL to import the schema. The schemaLocation used
  for this is a workspace relative path, e.g.
  schemaLocation="../MySchemaLib/MySchema.xsd".
  
  When an
  Integration Service is deployed to an integration service, the
  WSDL document can be downloaded by querying the service URL
  with the ?wsdl parameter, e.g.
  https://localhost:7843/MySoapService?wsdl. The WSDL document
  served from this endpoint rewrites schemaLocations for schemas
  defined in the application, or libraries so that they can be
  downloaded by service consumers. These are served from
  ?xsd=xsdN endpoints and are also have any schemaLocations
  rewritten if they reference application or library schemas.
  
  In
  ACE v11, if these schemas are referenced from a static library,
  rather than a shared library, the schemaLocations are not
  rewritten (so they remain as workspace relative paths) and
  these schemas cannot be downloaded using a ?xsd=xsdN endpoint.
  

Local fix

• Place the referenced schemas in a shared library rather than a
  static library.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of Integration Services in IBM App Connect Enterprise
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  <div><div><span style="color:#000000">If an XSD in a static
  library is referenced in the Integration Service description,
  for example as a request or response type for an operation, an
  <xsd:import> or <xsd:include></span><span style="color:#000000">
  element is added to the WSDL to import the schema. The
  schemaLocation used for this is a workspace relative path, e.g.
  schemaLocation="../MySchemaLib/MySchema.xsd".</span></div>
  <div><span style="color:#000000">When an Integration Service is
  deployed to an integration server, the WSDL document can be
  downloaded by querying the service URL with the ?wsdl parameter,
  e.g.</span></div><div><span
  style="color:#000000">https://localhost:7843/MySoapService?wsdl.
   The WSDL document served from this endpoint rewrites
  schemaLocations for schemas defined in the application, or
  libraries so that they can be downloaded by service consumers.
  These are served from ?xsd=xsdN endpoints and are also have any
  schemaLocations rewritten if they reference application or
  library schemas.</span></div> <div><span
  style="color:#000000">In ACE v11 and v12, if these schemas are
  referenced from a static library, rather than a shared library,
  the schemaLocations are not rewritten (so they remain as
  workspace relative paths) and these schemas cannot be downloaded
  using a ?xsd=xsdN endpoint.</span></div></div>
  

Problem conclusion

• WSDL documents for Integration Services now display the correct
  URL for imported schemas in static libraries.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v11.0      11.0.0.17
  v12.0      12.0.4.0
  
  The latest available maintenance can be obtained from:
  http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available,information on
  its planned availability can be found on:
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

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 CONNECT ENT

• Fixed component ID

  5724J0550

Applicable component levels