Error while creating a deployable proxy for a URL in NWDS

Question

Hi ,
There is a requirement for calling a webservice in the .NET platform from JAVA using NWDS. The webservice of the server is pinged using the URL of the webservice. when the URL is passed in the WS navigator of CRD ( that is Development Server) ,  the response is retreived successfully .  The version of NWDS is 7.0.23.
we are facing problem when we are trying to create a Deployable proxy in NWDS by using the following steps :
1) Create a Development Component
2) Select the Deployable Proxy
3) Create the Client Proxy Defintion of the created DC
At step 3 , when we giving the url or WSDL link  like "http:// www3.authoring.syngenta/newswebservice.asmx?WSDL" (this is just for example) , it is showing as "Invalid wsdl or wsdl not found " . so  that we are not able to procees further.
When we are trying to create proxy the for the WSDL link like " http:// www.authoring.syngenta/newswebservice.asmx?WSDL" , we are able to create successfully.
can anyone suggest why we are able to create the proxy for the URL "http:// www.authoring.syngenta/newswebservice.asmx?WSDL" and not for the other URL.
Any pointers or suggestions are very helpful.
Thanks and Regards,
Sreedevi

Answer 1

Late response I know, but I have solved a similar problem recently and thought I would share.
Firstly, the problem is not with the namespace. The "Namespace ..." part is just stating the namespace the "Incorrect Value" has. So this error is complaining about the value "Unknown" - which isn't very helpful.
It appears the SAP SE80 importer does not like elements like the following because it can't understand <s:element ref="s:schema" />. It appears this is a common thing to be included in .NET generated WSDLs.
 <s:element minOccurs="0" maxOccurs="1" name="GetCursDynamicResult">      <s:complexType>          <s:sequence>               <s:element ref="s:schema" />               <s:any />          </s:sequence>     </s:complexType></s:element> 
SAP will also not like this example as it does not support mixed content (see: http://www.w3schools.com/schema/schema_complex_mixed.asp)
<s:element minOccurs="0" maxOccurs="1" name="SaldoXMLResult">
     <s:complexType mixed="true">
          <s:sequence>
               <s:any />
          </s:sequence>
     </s:complexType>
</s:element>
You can "Fix" the problem in both cases by removing the offending text in a local copy of the WSDL file so remove line 4 in the first example and change line 2 in the second to <s:complexType> the proxy can then be generated. No idea if the resulting service will be fully operational though!