[JBoss JIRA] Created: (JBESB-2052) EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET
12:14 a.m.
EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET
-------------------------------------------------------------------------------
Key: JBESB-2052
URL: https://jira.jboss.org/jira/browse/JBESB-2052
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.4
Reporter: Burr Sutter
The WSDL and the quickstart that creates it are attached.
Here is the exact error message from Visual Studio/Visual Basic:
Error 1 Custom tool error: Unable to import WebService/Schema. Unable to import binding
'FetchCustomerBinding' from namespace
'http://soa.jboss.org/ESBWebServiceSample'. The operation
'FetchCustomerOp' on portType 'FetchCustomerPortType' from namespace
'http://soa.jboss.org/ESBWebServiceSample' had the following syntax error: The
operation has no matching binding. Check if the operation, input and output names in the
Binding section match with the corresponding names in the PortType
section. C:\Users\Burr\AppData\Local\Temporary Projects\WindowsApplication1\My
Project\Settings.settings 1 1 WindowsApplication1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:16 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2052) EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET
[
https://jira.jboss.org/jira/browse/JBESB-2052?page=com.atlassian.jira.plu...
]
Burr Sutter updated JBESB-2052:
-------------------------------
Attachment: FetchCustomer.wsdl
The generated WSDL
EBWS: WSDL produced by ESB Based Web Service endpoint is not
consumable by .NET
-------------------------------------------------------------------------------
Key: JBESB-2052
URL: https://jira.jboss.org/jira/browse/JBESB-2052
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.4
Reporter: Burr Sutter
Attachments: FetchCustomer.wsdl, publish_as_webservice2.zip
The WSDL and the quickstart that creates it are attached.
Here is the exact error message from Visual Studio/Visual Basic:
Error 1 Custom tool error: Unable to import WebService/Schema. Unable to import binding
'FetchCustomerBinding' from namespace
'http://soa.jboss.org/ESBWebServiceSample'. The operation
'FetchCustomerOp' on portType 'FetchCustomerPortType' from namespace
'http://soa.jboss.org/ESBWebServiceSample' had the following syntax error: The
operation has no matching binding. Check if the operation, input and output names in the
Binding section match with the corresponding names in the PortType
section. C:\Users\Burr\AppData\Local\Temporary Projects\WindowsApplication1\My
Project\Settings.settings 1 1 WindowsApplication1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:16 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2052) EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET
[
https://jira.jboss.org/jira/browse/JBESB-2052?page=com.atlassian.jira.plu...
]
Burr Sutter updated JBESB-2052:
-------------------------------
Attachment: publish_as_webservice2.zip
The quickstart that renders the WSDL.
EBWS: WSDL produced by ESB Based Web Service endpoint is not
consumable by .NET
-------------------------------------------------------------------------------
Key: JBESB-2052
URL: https://jira.jboss.org/jira/browse/JBESB-2052
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.4
Reporter: Burr Sutter
Attachments: FetchCustomer.wsdl, publish_as_webservice2.zip
The WSDL and the quickstart that creates it are attached.
Here is the exact error message from Visual Studio/Visual Basic:
Error 1 Custom tool error: Unable to import WebService/Schema. Unable to import binding
'FetchCustomerBinding' from namespace
'http://soa.jboss.org/ESBWebServiceSample'. The operation
'FetchCustomerOp' on portType 'FetchCustomerPortType' from namespace
'http://soa.jboss.org/ESBWebServiceSample' had the following syntax error: The
operation has no matching binding. Check if the operation, input and output names in the
Binding section match with the corresponding names in the PortType
section. C:\Users\Burr\AppData\Local\Temporary Projects\WindowsApplication1\My
Project\Settings.settings 1 1 WindowsApplication1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:05 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2052) EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET
[
https://jira.jboss.org/jira/browse/JBESB-2052?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-2052:
--------------------------------
Fix Version/s: 4.4 CP1
EBWS: WSDL produced by ESB Based Web Service endpoint is not
consumable by .NET
-------------------------------------------------------------------------------
Key: JBESB-2052
URL: https://jira.jboss.org/jira/browse/JBESB-2052
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.4
Reporter: Burr Sutter
Fix For: 4.4 CP1
Attachments: FetchCustomer.wsdl, publish_as_webservice2.zip
The WSDL and the quickstart that creates it are attached.
Here is the exact error message from Visual Studio/Visual Basic:
Error 1 Custom tool error: Unable to import WebService/Schema. Unable to import binding
'FetchCustomerBinding' from namespace
'http://soa.jboss.org/ESBWebServiceSample'. The operation
'FetchCustomerOp' on portType 'FetchCustomerPortType' from namespace
'http://soa.jboss.org/ESBWebServiceSample' had the following syntax error: The
operation has no matching binding. Check if the operation, input and output names in the
Binding section match with the corresponding names in the PortType
section. C:\Users\Burr\AppData\Local\Temporary Projects\WindowsApplication1\My
Project\Settings.settings 1 1 WindowsApplication1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:14 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2052) EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET
[
https://jira.jboss.org/jira/browse/JBESB-2052?page=com.atlassian.jira.plu...
]
Jim Ma commented on JBESB-2052:
-------------------------------
The generated wsdl is valid , and it is WSDL1.0 and WSI-BP compliant . But it does not
conform to the .Net own specification. We thought it is an issue in svcUtil.exe (.Net ws
code generation tool) and reported two years before , but .Net will not fix it.
The workaround for this issue is adding the name for <wsdl:input> and
<wsdl:output> in soapbinding :
<wsdl:binding name="FetchCustomerBinding"
type="tns:FetchCustomerPortType">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="FetchCustomerOp">
<wsdl:input name="FetchCustomerReq">
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output name="FetchCustomerRes">
<soap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="fault1">
<soap:fault name="fault1" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
EBWS: WSDL produced by ESB Based Web Service endpoint is not
consumable by .NET
-------------------------------------------------------------------------------
Key: JBESB-2052
URL: https://jira.jboss.org/jira/browse/JBESB-2052
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.4
Reporter: Burr Sutter
Fix For: 4.4 CP1
Attachments: FetchCustomer.wsdl, publish_as_webservice2.zip
The WSDL and the quickstart that creates it are attached.
Here is the exact error message from Visual Studio/Visual Basic:
Error 1 Custom tool error: Unable to import WebService/Schema. Unable to import binding
'FetchCustomerBinding' from namespace
'http://soa.jboss.org/ESBWebServiceSample'. The operation
'FetchCustomerOp' on portType 'FetchCustomerPortType' from namespace
'http://soa.jboss.org/ESBWebServiceSample' had the following syntax error: The
operation has no matching binding. Check if the operation, input and output names in the
Binding section match with the corresponding names in the PortType
section. C:\Users\Burr\AppData\Local\Temporary Projects\WindowsApplication1\My
Project\Settings.settings 1 1 WindowsApplication1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:30 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2052) EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET
[
https://jira.jboss.org/jira/browse/JBESB-2052?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2052:
-------------------------------------
Thanks for the description Jim, extremely helpful :)
EBWS: WSDL produced by ESB Based Web Service endpoint is not
consumable by .NET
-------------------------------------------------------------------------------
Key: JBESB-2052
URL: https://jira.jboss.org/jira/browse/JBESB-2052
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.4
Reporter: Burr Sutter
Assignee: Kevin Conner
Fix For: 4.4 CP1
Attachments: FetchCustomer.wsdl, publish_as_webservice2.zip
The WSDL and the quickstart that creates it are attached.
Here is the exact error message from Visual Studio/Visual Basic:
Error 1 Custom tool error: Unable to import WebService/Schema. Unable to import binding
'FetchCustomerBinding' from namespace
'http://soa.jboss.org/ESBWebServiceSample'. The operation
'FetchCustomerOp' on portType 'FetchCustomerPortType' from namespace
'http://soa.jboss.org/ESBWebServiceSample' had the following syntax error: The
operation has no matching binding. Check if the operation, input and output names in the
Binding section match with the corresponding names in the PortType
section. C:\Users\Burr\AppData\Local\Temporary Projects\WindowsApplication1\My
Project\Settings.settings 1 1 WindowsApplication1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:30 p.m.
New subject: [JBoss JIRA] Assigned: (JBESB-2052) EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET
[
https://jira.jboss.org/jira/browse/JBESB-2052?page=com.atlassian.jira.plu...
]
Kevin Conner reassigned JBESB-2052:
-----------------------------------
Assignee: Kevin Conner
EBWS: WSDL produced by ESB Based Web Service endpoint is not
consumable by .NET
-------------------------------------------------------------------------------
Key: JBESB-2052
URL: https://jira.jboss.org/jira/browse/JBESB-2052
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.4
Reporter: Burr Sutter
Assignee: Kevin Conner
Fix For: 4.4 CP1
Attachments: FetchCustomer.wsdl, publish_as_webservice2.zip
The WSDL and the quickstart that creates it are attached.
Here is the exact error message from Visual Studio/Visual Basic:
Error 1 Custom tool error: Unable to import WebService/Schema. Unable to import binding
'FetchCustomerBinding' from namespace
'http://soa.jboss.org/ESBWebServiceSample'. The operation
'FetchCustomerOp' on portType 'FetchCustomerPortType' from namespace
'http://soa.jboss.org/ESBWebServiceSample' had the following syntax error: The
operation has no matching binding. Check if the operation, input and output names in the
Binding section match with the corresponding names in the PortType
section. C:\Users\Burr\AppData\Local\Temporary Projects\WindowsApplication1\My
Project\Settings.settings 1 1 WindowsApplication1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:32 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-2052) EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET
[
https://jira.jboss.org/jira/browse/JBESB-2052?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-2052:
--------------------------------
Attachment: FetchCustomer.new.wsdl
Burr, I have made the changes to the code as described by Jim.
Could you verify that the attached WSDL works for you? If so I will commit the changes.
EBWS: WSDL produced by ESB Based Web Service endpoint is not
consumable by .NET
-------------------------------------------------------------------------------
Key: JBESB-2052
URL: https://jira.jboss.org/jira/browse/JBESB-2052
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.4
Reporter: Burr Sutter
Assignee: Kevin Conner
Fix For: 4.4 CP1
Attachments: FetchCustomer.new.wsdl, FetchCustomer.wsdl,
publish_as_webservice2.zip
The WSDL and the quickstart that creates it are attached.
Here is the exact error message from Visual Studio/Visual Basic:
Error 1 Custom tool error: Unable to import WebService/Schema. Unable to import binding
'FetchCustomerBinding' from namespace
'http://soa.jboss.org/ESBWebServiceSample'. The operation
'FetchCustomerOp' on portType 'FetchCustomerPortType' from namespace
'http://soa.jboss.org/ESBWebServiceSample' had the following syntax error: The
operation has no matching binding. Check if the operation, input and output names in the
Binding section match with the corresponding names in the PortType
section. C:\Users\Burr\AppData\Local\Temporary Projects\WindowsApplication1\My
Project\Settings.settings 1 1 WindowsApplication1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:49 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2052) EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET
[
https://jira.jboss.org/jira/browse/JBESB-2052?page=com.atlassian.jira.plu...
]
Burr Sutter commented on JBESB-2052:
------------------------------------
The new error message is:
Custom tool error: Unable to import WebService/Schema. Unable to import binding
'FetchCustomerBinding' from namespace
'http://soa.jboss.org/ESBWebServiceSample'. Unable to import operation
'FetchCustomerOp'. The operation binding 'FetchCustomerOp' from namespace
'http://soa.jboss.org/ESBWebServiceSample' had invalid syntax. Missing
soap:operation binding. C:\Users\Burr\Documents\Visual Studio
2008\Projects\WindowsApplication1\WindowsApplication1\My
Project\Settings.settings 1 1 WindowsApplication1
EBWS: WSDL produced by ESB Based Web Service endpoint is not
consumable by .NET
-------------------------------------------------------------------------------
Key: JBESB-2052
URL: https://jira.jboss.org/jira/browse/JBESB-2052
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.4
Reporter: Burr Sutter
Assignee: Kevin Conner
Fix For: 4.4 CP1
Attachments: FetchCustomer.new.wsdl, FetchCustomer.wsdl,
publish_as_webservice2.zip
The WSDL and the quickstart that creates it are attached.
Here is the exact error message from Visual Studio/Visual Basic:
Error 1 Custom tool error: Unable to import WebService/Schema. Unable to import binding
'FetchCustomerBinding' from namespace
'http://soa.jboss.org/ESBWebServiceSample'. The operation
'FetchCustomerOp' on portType 'FetchCustomerPortType' from namespace
'http://soa.jboss.org/ESBWebServiceSample' had the following syntax error: The
operation has no matching binding. Check if the operation, input and output names in the
Binding section match with the corresponding names in the PortType
section. C:\Users\Burr\AppData\Local\Temporary Projects\WindowsApplication1\My
Project\Settings.settings 1 1 WindowsApplication1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:32 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-2052) EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET
[
https://jira.jboss.org/jira/browse/JBESB-2052?page=com.atlassian.jira.plu...
]
Kevin Conner closed JBESB-2052.
-------------------------------
Resolution: Done
WSDL generation has been fixed in revision 22930.
Burr confirmed that the new WSDL fixes the issue.
EBWS: WSDL produced by ESB Based Web Service endpoint is not
consumable by .NET
-------------------------------------------------------------------------------
Key: JBESB-2052
URL: https://jira.jboss.org/jira/browse/JBESB-2052
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.4
Reporter: Burr Sutter
Assignee: Kevin Conner
Fix For: 4.4 CP1
Attachments: FetchCustomer.new.wsdl, FetchCustomer.wsdl,
publish_as_webservice2.zip
The WSDL and the quickstart that creates it are attached.
Here is the exact error message from Visual Studio/Visual Basic:
Error 1 Custom tool error: Unable to import WebService/Schema. Unable to import binding
'FetchCustomerBinding' from namespace
'http://soa.jboss.org/ESBWebServiceSample'. The operation
'FetchCustomerOp' on portType 'FetchCustomerPortType' from namespace
'http://soa.jboss.org/ESBWebServiceSample' had the following syntax error: The
operation has no matching binding. Check if the operation, input and output names in the
Binding section match with the corresponding names in the PortType
section. C:\Users\Burr\AppData\Local\Temporary Projects\WindowsApplication1\My
Project\Settings.settings 1 1 WindowsApplication1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:34 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2052) EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET
[
https://jira.jboss.org/jira/browse/JBESB-2052?page=com.atlassian.jira.plu...
]
Marcin Budny commented on JBESB-2052:
-------------------------------------
Can you please write what was the resolution to this problem?
EBWS: WSDL produced by ESB Based Web Service endpoint is not
consumable by .NET
-------------------------------------------------------------------------------
Key: JBESB-2052
URL: https://jira.jboss.org/jira/browse/JBESB-2052
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.4
Reporter: Burr Sutter
Assignee: Kevin Conner
Fix For: 4.4 CP1
Attachments: FetchCustomer.new.wsdl, FetchCustomer.wsdl,
publish_as_webservice2.zip
The WSDL and the quickstart that creates it are attached.
Here is the exact error message from Visual Studio/Visual Basic:
Error 1 Custom tool error: Unable to import WebService/Schema. Unable to import binding
'FetchCustomerBinding' from namespace
'http://soa.jboss.org/ESBWebServiceSample'. The operation
'FetchCustomerOp' on portType 'FetchCustomerPortType' from namespace
'http://soa.jboss.org/ESBWebServiceSample' had the following syntax error: The
operation has no matching binding. Check if the operation, input and output names in the
Binding section match with the corresponding names in the PortType
section. C:\Users\Burr\AppData\Local\Temporary Projects\WindowsApplication1\My
Project\Settings.settings 1 1 WindowsApplication1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:49 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2052) EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET
[
https://jira.jboss.org/jira/browse/JBESB-2052?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2052:
-------------------------------------
It is fixed in 4.4CP1 and will be released as part of ESB 4.5.
EBWS: WSDL produced by ESB Based Web Service endpoint is not
consumable by .NET
-------------------------------------------------------------------------------
Key: JBESB-2052
URL: https://jira.jboss.org/jira/browse/JBESB-2052
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.4
Reporter: Burr Sutter
Assignee: Kevin Conner
Fix For: 4.4 CP1
Attachments: FetchCustomer.new.wsdl, FetchCustomer.wsdl,
publish_as_webservice2.zip
The WSDL and the quickstart that creates it are attached.
Here is the exact error message from Visual Studio/Visual Basic:
Error 1 Custom tool error: Unable to import WebService/Schema. Unable to import binding
'FetchCustomerBinding' from namespace
'http://soa.jboss.org/ESBWebServiceSample'. The operation
'FetchCustomerOp' on portType 'FetchCustomerPortType' from namespace
'http://soa.jboss.org/ESBWebServiceSample' had the following syntax error: The
operation has no matching binding. Check if the operation, input and output names in the
Binding section match with the corresponding names in the PortType
section. C:\Users\Burr\AppData\Local\Temporary Projects\WindowsApplication1\My
Project\Settings.settings 1 1 WindowsApplication1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:55 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2052) EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET
[
https://jira.jboss.org/jira/browse/JBESB-2052?page=com.atlassian.jira.plu...
]
Marcin Budny commented on JBESB-2052:
-------------------------------------
Kevin, thanks for reply, but I wanted to know what exactly was causing the problem. The
attached FetchCustomer.new.wsdl doesn't work for me either when using .NET's
wsdl.exe tool to generate proxy. I get same error Burr got second time. I'm trying to
generate proxy for testing purposes and I would like to manually edit the WSDL.
EBWS: WSDL produced by ESB Based Web Service endpoint is not
consumable by .NET
-------------------------------------------------------------------------------
Key: JBESB-2052
URL: https://jira.jboss.org/jira/browse/JBESB-2052
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.4
Reporter: Burr Sutter
Assignee: Kevin Conner
Fix For: 4.4 CP1
Attachments: FetchCustomer.new.wsdl, FetchCustomer.wsdl,
publish_as_webservice2.zip
The WSDL and the quickstart that creates it are attached.
Here is the exact error message from Visual Studio/Visual Basic:
Error 1 Custom tool error: Unable to import WebService/Schema. Unable to import binding
'FetchCustomerBinding' from namespace
'http://soa.jboss.org/ESBWebServiceSample'. The operation
'FetchCustomerOp' on portType 'FetchCustomerPortType' from namespace
'http://soa.jboss.org/ESBWebServiceSample' had the following syntax error: The
operation has no matching binding. Check if the operation, input and output names in the
Binding section match with the corresponding names in the PortType
section. C:\Users\Burr\AppData\Local\Temporary Projects\WindowsApplication1\My
Project\Settings.settings 1 1 WindowsApplication1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:38 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2052) EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET
[
https://jira.jboss.org/jira/browse/JBESB-2052?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2052:
-------------------------------------
Please discuss this on the forums in that case, we can follow up there.
EBWS: WSDL produced by ESB Based Web Service endpoint is not
consumable by .NET
-------------------------------------------------------------------------------
Key: JBESB-2052
URL: https://jira.jboss.org/jira/browse/JBESB-2052
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.4
Reporter: Burr Sutter
Assignee: Kevin Conner
Fix For: 4.4 CP1
Attachments: FetchCustomer.new.wsdl, FetchCustomer.wsdl,
publish_as_webservice2.zip
The WSDL and the quickstart that creates it are attached.
Here is the exact error message from Visual Studio/Visual Basic:
Error 1 Custom tool error: Unable to import WebService/Schema. Unable to import binding
'FetchCustomerBinding' from namespace
'http://soa.jboss.org/ESBWebServiceSample'. The operation
'FetchCustomerOp' on portType 'FetchCustomerPortType' from namespace
'http://soa.jboss.org/ESBWebServiceSample' had the following syntax error: The
operation has no matching binding. Check if the operation, input and output names in the
Binding section match with the corresponding names in the PortType
section. C:\Users\Burr\AppData\Local\Temporary Projects\WindowsApplication1\My
Project\Settings.settings 1 1 WindowsApplication1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5643
days inactive
5761
days old
13 comments
4 participants
participants (4)
-
Burr Sutter (JIRA) -
Jim Ma (JIRA)
-
Kevin Conner (JIRA)
-
Marcin Budny (JIRA)