Originally posted by: SystemAdmin

Is the wsdl importer part of the 8.2.0.4 install or does that require additional pack?

I am getting the following when I try to import a wsdl, jsut being able to see the WSDL as an option on import seems that it is there:

java.lang.Exception: com.ibm.websphere.dtx.xmlsimp75.SchemaException
at com.ibm.websphere.dtx.wsdlImp.WSDLImporter.writeXmlSchemaMTS(WSDLImporter.java:2889)
at com.ibm.websphere.dtx.wsdlImp.WSDLImporter.writeMts(WSDLImporter.java:4048)
at com.ibm.websphere.dtx.wsdlImp.WSDLImporter.generateMTS(WSDLImporter.java:2029)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at com.ibm.websphere.dtx.ui.importers.wsdl.WSDLTXImporter.generateTree(Unknown Source)
at com.ibm.websphere.dtx.ui.importers.dialogs.WTXImportWizard.buildTypeTree(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)
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: lanapoli

The WSDL importer is part of 8.2.0.4. Does your WSDL refer to a schema ad if so, is it available? Can that schema be imported successfully? I can look at it if you post the WSDL and relevant schemas.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Yes, wsdl imports to many schemas. I can create a project in SoapUI with the same wsdl from the same location to that tells me all of the schemas are accessible. Just not getting much information out of the import to determine what it does not like. I can't post the source given the client.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: Liv2luv

You might want to consider re-installing WTX as an option. Also there was an interim Fix try applying it. Here is the link : http://www-01.ibm.com/support/docview.wss?rs=2320&context=SSVSD8&dc=D400&uid=swg24025289&loc=en_US&cs=UTF-8&lang=en
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

I installed ifix3 and the same result. I am going to compare to another wsdl that does import and see if I can track down what is causing the importer to fail. Remembering that it does import/validate in other tools (SoapScope, SoapUI, XMLPad...)
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: paul.brett

If your WSDL includes this line:

<s:element ref="s:schema"/>

...then you will also need a line such as this:

<s:import namespace="http://www.w3.org/2001/XMLSchema"/>

...then your WSDL should import without the exception.

Hope that helps.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

No, there are not any cases where the schema are not called out when used as references. The one bit of information that I am getting is the error popup that indicates "error find wsdl operations" with Reason of "Error parsing wsdl file and finding list of operations". The wsdl has been validated in several different tools and loaded/validated on datapower as well.

I am at a lost and think I will open up a pmr.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender