I had a similar experience, not sure if this will solve your problem.
I had imported a WSDL in flex 3.0 beta 2. While working with the
action script code it generated, specificially adding any code
related to SOAP, the import statements would change automatically,
leaving out several libraries including the following two;
import mx.messaging.ChannelSet;
import mx.messaging.channels.DirectHTTPChannel;
I reimported the WSDL and saved a copy of the libraries. The was
getting was a compile-time error.
--- In [email protected], Christoph Guse <[EMAIL PROTECTED]> wrote:
>
> Hi List,
>
> I try to configure the flex webservice proxy in proxy-config.xml
and it
> drives me crazy. I'm not able to load the WSDL from a Webservice
which
> is secured by SSL ( self signed Certificate ) and
BasicAuthentication. I
> searched the docs but I was not abel to find a complete example.
Even
> the description in the lcds development guide doesn't help.
>
> *Destination in proxy-config.xml*
> <destination id="dataElements">
> <adapter ref="soap-proxy" />
> <channels>
> <channel ref="my-secure-http" />
> </channels>
> <properties>
>
> <wsdl>https://eipref1.kingmedia.de/ws/getDataElements?wsdl</wsdl>
>
<soap>https://eipref1.kingmedia.de/ws/getDataElements</soap>
> <remote-username>John Doe</remote-username>
> <remote-password>doe</remote-password>
> </properties>
> </destination>
>
> *Webservice declaration in mxml*
> <mx:WebService id="dataElementService"
destination="dataElements"
> useProxy="true" showBusyCursor="true">
> <mx:operation name="getDataElements" concurrency="multiple"
> resultFormat="e4x" />
> </mx:WebService>
>
> *WS call in method*
> dataElementService.getDataElements([ws specific argument]);
>
> *Error message in application*
> [RPC Fault faultString="[MessagingError message='Destination
> 'dataElements' has no channels defined and the application does not
> define any default channels.']" faultCode="InvokeFailed"
> faultDetail="Unable to load WSDL. If currently online, please
verify the
> URI and/or format of the WSDL (null)"]
> at
> mx.rpc.wsdl::WSDLLoader/faultHandler()
[E:\dev\flex_201_borneo\sdk\frameworks\mx\rpc\wsdl\WSDLLoader.as:76]
> at flash.events::EventDispatcher/dispatchEventFunction()
> at flash.events::EventDispatcher/dispatchEvent()
> at
>
mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::di
spatchRpcEvent()
[E:\dev\flex_201_borneo\sdk\frameworks\mx\rpc\AbstractInvoker.as:146]
> at Function/http://adobe.com/AS3/2006/builtin::apply()
> at
> mx.rpc::AsyncDispatcher/timerEventHandler()
[E:\dev\flex_201_borneo\sdk\frameworks\mx\rpc\AsyncDispatcher.as:57]
> at flash.utils::Timer/_timerDispatch()
> at flash.utils::Timer/tick()
>
> I'm using LCDS 2.5 ES and the Flex 2.0.1 Hotfix 3 compilter
delivered
> with FB Beta3.
>
> I tried to use Ethereal to see which information is send to the WS
but
> that wasn't successfull.
>
> The webservice itself is created with JAX-WS 2.1 and works like a
charm,
> tested with SoapUI 2.0.
>
> At the moment I have no idea why I can't call my webservice. Can
> somebody help me, please?
>
> Regards,
> Christoph
>
