[fteran]

When I try to generate new web service clients I get the following WSDL Validation error:
WS-I: (BP2402) The wsdl:binding element does not use a sopabind:binding element as defined in section “3 SOAP Binding.” of the WSDL 1.1 specification

I am getting this error message for all these WSDLs:
http://www.webservicex.net/CurrencyConvertor.asmx?WSDL
http://www.webservicex.net/ConvertTemperature.asmx?WSDL

Here is myeclipse installation details:
*** Date:
Monday, December 17, 2012 4:54:53 PM CST

*** System properties:
OS=WindowsVista
OS version=6.1.0
OS arch=amd64
Profile arch=x86_64
Window system=win32
Java version=1.6.0_13
Workspace=file:/D:/workspaces/csi/
VM Args=-Xmx512m
-XX:MaxPermSize=256m
-XX:ReservedCodeCacheSize=64m
-Dosgi.nls.warnings=ignore
-Duser.name=Fernando Teran
-jar
C:\Users\fteran\AppData\Local\MYECLI~1\MYECLI~1\../Common/plugins/ORB7B5~1.JAR

*** Subscription information
Product Id: E3MS (MyEclipse for Spring Subscription)
License version: 3.0
Full Maintenance Included
Subscription expiration date (YYYYMMDD): 20131217
Number of users: 1

*** Eclipse details:
MyEclipse for Spring

Version: 10.6.0

Build ID: 10.6.0-20120831

Blueprint: MyEclipse for Spring 10

Eclipse startup command=-os
win32
-ws
win32
-arch
x86_64
-showsplash
-launcher
C:\Users\fteran\AppData\Local\MyEclipse for Spring\MyEclipse for Spring 10\myeclipseforspring.exe
-name
Myeclipseforspring
–launcher.library
C:\Users\fteran\AppData\Local\MyEclipse for Spring\MyEclipse for Spring 10\../Common/plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_64_4.2.0.v201201111650\eclipse_4201.dll
-startup
C:\Users\fteran\AppData\Local\MyEclipse for Spring\MyEclipse for Spring 10\../Common/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
-exitdata
1b38_5c
-install
C:\Users\fteran\AppData\Local\MyEclipse for Spring\MyEclipse for Spring 10
-configuration
C:\Users\fteran\AppData\Local\MyEclipse for Spring\MyEclipse for Spring 10\configuration
-vm
C:\Users\fteran\AppData\Local\MyEclipse for Spring\Common\binary\com.sun.java.jdk.win32.x86_64_1.6.0.013\bin\javaw.exe

Thank you for your help,
Fernando

[support-pradeep]

fteran,

WS-I is primarily an “interoperability” standard allowing web services developed using one particular framework / stack to be used or consumed by other frameworks with the least possible pain. So what is happening here is just that, you are running into a few issues because your client is not WS-I compliant.

Given the fact that you are generating the web service client and not the web service itself, I would feel that most of the WS-I errors are not important and can be ignored. It would always be useful to have your client make his WSDL WS-I compliant, but that is often not viable in many instances.

[Author]

Posts