Is the wsdl you are using is publicly available?
If so, please provide the wsdl URL.
Also, can you make sure that destinations are defined correctly in proxy-config.xml
WSDL is not on public domain.
Sending contents of wsdl
xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!-- Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.4-b01-. -->
definitions targetNamespace="http://webservice.flexsampleservlet.u0.deere.com/" name="CustomerWS" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://webservice.flexsampleservlet.u0.deere.com/" xmlns="http://schemas.xmlsoap.org/wsdl/">
<xsd:import namespace="http://webservice.flexsampleservlet.u0.deere.com/" schemaLocation="CustomerWS_schema1.xsd"/>
Is import of xsd supported by flex webservice connection wizard
Destination is configured correctly as I can make call to webservice using destination configured in LCDS from flex application
Destination is configured on LCDS is correct as I can get data from it in flex application using webservice tag
<s:WebService id = "customerWS" destination="customerWSDestination" useProxy="true" />
Webservice is not on public domain.
I am sending wsdl for your reference.
Please send us details about 'CustomerWS_schema1.xsd'.
Also looks like the schema you have attached is incomplete.
Does it contain any operation,binding etc?
I configured following destination in proxy-config.xml
But this destination is also not displayed in Flash builder 4 -- data connect wizard of webservice.
I configured remoting service and I can see remoting destination in lcds data connect wizard.
Can someone send me destination configuration of webservice configured with public wsdl which works with Flash Builder 4 release version webservice data connect wizard.
Please modify your configuration in proxy-config.xml to:
Looks like you missed the adapter definition.
Please let us know after making this change, restart your server and try the workflow.
It works for us here.
After setting adapter in destination it worked.
Thanks Sridar for solving our problem.