IBM Support

PM46197: JAVA EXCEPTION WHEN IMPORTING A WSDL FILE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The following 'java.lang.Exception:
    com.ibm.websphere.dtx.xmlsimp75.SchemaException' occurs when
    importing a WSDL file.
    
    errors java.lang.Exception:
    com.ibm.websphere.dtx.xmlsimp75.SchemaException
     at
    com.ibm.websphere.dtx.wsdlImp.WSDLImporter.writeXmlSchemaMTS(WSD
    LImporter.java:2954)
     at
    com.ibm.websphere.dtx.wsdlImp.WSDLImporter.writeMts(WSDLImporter
    .java:4333)
     at
    com.ibm.websphere.dtx.wsdlImp.WSDLImporter.generateMTS(WSDLImpor
    ter.java:2088)
     at
    com.ibm.websphere.dtx.wsdlImp.WSDLImporter.generateMTS(WSDLImpor
    ter.java:2037)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.java:79)
     at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:43)
     at java.lang.reflect.Method.invoke(Method.java:618)
     at
    com.ibm.websphere.dtx.ui.importers.wsdl.WSDLTXImporter.generateT
    ree(Unknown Source)
     at
    com.ibm.websphere.dtx.ui.importers.dialogs.WTXImportWizard.build
    TypeTree(Unknown Source)
     at
    com.ibm.websphere.dtx.ui.importers.dialogs.WTXImportWizard$2.run
    (Unknown Source)
     at
    org.eclipse.jface.operation.ModalContext$ModalContextThread.run(
    ModalContext.java:113)
    

Local fix

  • WTXCQ - WTX00038423
    GK / GK
    Circumvention: Perform the following steps avoid the problem.
    
    1. Copy included schema files into the local WSDL directory.
    
    2. Change the "include" references to simply contain the xsd
       file name, but no path.
    

Problem summary

  • Users Affected:
    WebSphere Transformation Extender user that generates type trees
    from a WSDL file that contains "include" references within the
    schema definition.
    
    Problem Description:
    A WSDL file that references schemas with nested "include"
    statements would not get imported properly.
    
    Platforms Affected:
    Windows
    

Problem conclusion

  • The XML schema "include" construct can properly handle nested
    relative path names.  Before this fix, multiple "include"
    constructs that were nested under different directory structures
    than the original wsdl file generated XML schema processing
    errors.
    
    Delivered in:
    8.1.0.6, 8.2.0.6, 8.3.0.5
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM46197

  • Reported component name

    WSTX

  • Reported component ID

    5724M4000

  • Reported release

    830

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2011-08-23

  • Closed date

    2011-09-23

  • Last modified date

    2012-02-03

  • 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

    WSTX

  • Fixed component ID

    5724M4000

Applicable component levels

  • R810 PSY

       UP

  • R820 PSY

       UP

  • R830 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSD8","label":"IBM Transformation Extender"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.3","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
03 February 2012