I have a working Java/Axis 1.4 web service running. With Visual Studio
2005, if I try to create a web reference and refresh the Axis service,
I get this error:
The custom tool 'MSDiscoCodegenerator' failes. Unabel to import
binding 'TestSvcSoapBinding' from namespace
'http://testxspace/test/mgt'.
So no types are available to Visual Studio. How can I fix this?
Thanks. I am running .NET 2.0 on XP with all WindowsUpdate patches.
Hello lucius,
From your description, you have an JAVA axis based web service, when using
visual studio 2005 "add webreference" to create the web proxy(refresh) it,
you will get error which cause the proxy code fail to be generated, correct?
Regarding on this issue, I think the problem should be related to the axis
webservice's WSDL document and the service proxy generation's code logic.
Since we haven't detailed info on the service proxy generation's internal
implement, I would suggest you first try using the wsdl.exe utility to try
creating the service proxy at commandline:
#Web Services Description Language Tool (Wsdl.exe)
http://msdn2.microsoft.com/en-us/library/7h3ystb6(VS.80).aspx
If the problem also occur through the commandline utility, it seems the
webservice's WSDL document has something conflict with the .net proxy
generation code logic.
Also, if possible, would you provide me a public link to the axis service
or at least its wsdl document so that I can try referencing it at my local
test environment?
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
lucius - 22 Feb 2007 03:25 GMT
Yes, you understand my problem.
Using the wsdl.exe app did not work either. Can I email the WSDL to
your online Microsoft address?
Thanks.
>Hello lucius,
>
[quoted text clipped - 18 lines]
>or at least its wsdl document so that I can try referencing it at my local
>test environment?
Steven Cheng[MSFT] - 22 Feb 2007 10:07 GMT
Sure, you can send me the WSDL file via email. However, notice that you
need to remove the "online" from the email address in my signature. The
address should be "stcheng" + "@" + "microsoft.com".
Looking forward to your message.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
lucius - 22 Feb 2007 21:38 GMT
The email plus WSDL attachment was emailed to you a couple of hours
ago. Could you please respond to that email address that you received
the email OK?
Thanks.
>Sure, you can send me the WSDL file via email. However, notice that you
>need to remove the "online" from the email address in my signature. The
[quoted text clipped - 9 lines]
>
>This posting is provided "AS IS" with no warranties, and confers no rights.
Steven Cheng[MSFT] - 23 Feb 2007 02:58 GMT
Hi lucius,
I have received your email with the "axis.wsdl"(62kb). I'll perform some
test and let you know my result.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
Steven Cheng[MSFT] - 26 Feb 2007 09:20 GMT
Hello Lucius,
After some further checking against the WSDL file and the error message
wsdl.exe raise, I've found out the cause of the problem. It is actually due
to the following type that is not correctly imported in the wsdl document:
=============
xmlns:apachesoap="http://xml.apache.org/xml-soap"
type="apachesoap:Element"
==============
there are many elements reference to the above "apachesoap:Element" type,
however, the schema definiation of this
type(http://xml.apache.org/xml-soap) is no longer available(seems a legacy
schema that has been removed). that result to the failure of validating
the whole WSDL document(actual those types which refer to that problem
type). Actually, you can see this validation warnning in XML Editor when
you open the wsdl file in VisualStudio IDE.
currently, I think you may consider the following options to resolve the
problem:
1. contact the apache webservice project to request the following schema
xmlns:apachesoap="http://xml.apache.org/xml-soap"
or if they have updated version on this(compatible with the original one),
you can try using the update schema. Use the <import> element to import
schema into your WSDL document.
2. I've tried remove all those " type="apachesoap:Element"" type
declaration and after that the proxy can be created correctly. The only
problem is that since the type info is missing, those elements(refer to the
problem type) will be mapped as "object" class in .net. anyway, you can get
this a try to see whether ti works.
Hope this helps. If there is anything unclear on this, please feel free to
let me know.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.