The detailed error message in this case is,

Channel.Connect.Failed error
Netconnection.Call.Failed:HTTP:Failed

My flex-remoting-service.xml looks as follows,

    <default-channels>
        <channel ref="my-amf"/>
    </default-channels>

    <destination id="EchoString">
        <properties>
            <source>samples.SimpleRemoteObject.Echo</source>
        </properties>
    </destination>
 
& the channel "my-amf" is defined in flex-enterprise-services.xml as
follows,

        <channel-definition id="my-amf"
class="mx.messaging.channels.AMFChannel">
            <endpoint
uri="http://{server.name}:{server.port}/{context.root}/messagebroker/amf"
class="flex.messaging.endpoints.AMFEndpoint"/>
            <properties>
                <polling-enabled>false</polling-enabled>
            </properties>
        </channel-definition>

Thanks,
Aejaz

--- In flexcoders@yahoogroups.com, "aejaz_98" <[EMAIL PROTECTED]> wrote:
>
> Hi Peter,
>
> Thanks for your reply & please disregard my previous message. I
> recompiled the application & now I am getting "send failed" error
> message. Can you please take a look at the mxml to see if anything
> is wrong. I am very new to mxml & might have had overlooked something
> obvious.
>
> Thanks,
> Aejaz
>
> <?xml version="1.0" encoding="utf-8"?>
> <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" xmlns="*"
> layout="absolute">
> <mx:Script>
>       <![CDATA[
>             import mx.rpc.events.*;
>             import mx.collections.*;
>             import mx.controls.*
>          
>           private function getNameHandler(event:ResultEvent):void
>           {
>                 Result.text = event.result.toString();
>                 currentState='TargetState';
>           }
>          
>             private function faultHandler(event:FaultEvent):void
>         {
>               Alert.show(event.fault.faultstring, "Error");     
>         }
>       ]]>
> </mx:Script>
>       <mx:states>
>             <mx:State name="TargetState">
>                   <mx:RemoveChild child="{button1}"/>
>                   <mx:RemoveChild child="{formInput}"/>
>                   <mx:RemoveChild child="{label1}"/>
>                   <mx:AddChild position="lastChild">
>                         <mx:Label x="99" y="130" width="265" height="28" id="Result"/>
>                   </mx:AddChild>
>             </mx:State>
>       </mx:states>
>
>       <mx:RemoteObject id="SendStringBack" destination="EchoString"
> showBusyCursor="true" fault="faultHandler(event)">
>             <mx:method name="getString" result="getNameHandler(event)">
>                   <mx:arguments>
>                         <str>
>                         {formInput.text}
>                         </str>
>                   </mx:arguments>
>             </mx:method>
>       </mx:RemoteObject>
>       <mx:TextInput x="119" y="129" id="formInput"/>
>       <mx:Button x="119" y="170" label="Submit" fontSize="13" id="button1"
> click="SendStringBack.getString.send()"/>
>       <mx:Label x="119" y="86" text="What is your name ?" width="160"
> fontSize="15" id="label1"/>     
> </mx:Application>
>
>
>
> --- In flexcoders@yahoogroups.com, "Peter Farland" <pfarland@> wrote:
> >
> > You must always point --services to the top level services file, which
> > is flex-enterprise-services.xml. The flex-remoting-service.xml is
merely
> > an include to this top level file (see the service-include tag
pointing
> > to this and the other services in the top level
> > flex-enterprise-services.xml file). It's ok to make changes to the
> > flex-remoting-service.xml file as it's included each time by the top
> > level file.
> >
> > That said, if you're changing destination settings in any of the
> > configuration and are using the --services option to codegen the
correct
> > information for you at runtime then you need to recompile the SWFs
> > everytime you make a change.
> >
> > Pete
> >
> > -----Original Message-----
> > From: flexcoders@yahoogroups.com
[mailto:[EMAIL PROTECTED] On
> > Behalf Of aejaz_98
> > Sent: Tuesday, April 25, 2006 10:10 AM
> > To: flexcoders@yahoogroups.com
> > Subject: [flexcoders] Re: (Flex20 Beta2): RemoteObject Destination
> > configuration problem
> >
> > Thanks for your reply. I am precompiling the SWFs using flex builder.
> > The value present in the "Additional compiler arguments" field is,
> >
> > -services
> > "C:\tomcat\webapps\flex\WEB-INF\flex\flex-enterprise-services.xml"
> >
> > when I change it to,
> >
> > -services
> > "C:\tomcat\webapps\flex\WEB-INF\flex\flex-remoting-service.xml"
> >
> > I start getting,
> >
> > exception 'java.lang.RuntimeException' while setting variable
> > 'compiler.services'. It seems that the only value allowed is
> > "C:\tomcat\webapps\flex\WEB-INF\flex\flex-enterprise-services.xml". I
> > tried putting,
> >
> >
"C:\tomcat\webapps\flex\WEB-INF\flex\flex-enterprise-services.xml;C:\tom
> > \
> > cat\webapps\flex\WEB-INF\flex\flex-remoting-service.xml"
> >
> > it gave me "Unable to open
> >
C:\tomcat\webapps\flex\WEB-INF\flex\flex-enterprise-services.xml;C:\tomc
> > \
> > at\webapps\flex\WEB-INF\flex\flex-remoting-service.xml
> >
> > Please let me know what does setting,
> >
> > -services
> >   C:\tomcat\webapps\flex\WEB-INF\flex\flex-remoting-service.xml"
> >
> > do & can't it be done manually.
> >
> > Thanks,
> > Aejaz
> >
> > --- In flexcoders@yahoogroups.com, "Peter Farland" <pfarland@> wrote:
> > >
> > > Are you precompiling the SWFs? If so, are you specifying --services
> > and
> > > pointing to the configuration file at compile time with either Flex
> > > Builder compiler command line arguments or mxmlc command line
> > arguments?
> > >
> >
> >
> >
> >
> >
> >
> >
> > --
> > Flexcoders Mailing List
> > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
> > Search Archives:
> > http://www.mail-archive.com/flexcoders%40yahoogroups.com
> > Yahoo! Groups Links
> >
>







--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




YAHOO! GROUPS LINKS




Reply via email to