RE: [flexcoders] Re: (Flex20 Beta2): send failed for RemoteObject
Ah, yes, you need to specify --context.root on the command line as the client can't tell what the context root is (i.e. because you can have the default context root it can't make assumptions as to whether the first level under the webroot is a subdirectory or a context root). -Original Message- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of aejaz_98 Sent: Tuesday, April 25, 2006 1:59 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: (Flex20 Beta2): send failed for RemoteObject 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 sourcesamples.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-enabledfalse/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
RE: [flexcoders] Re: (Flex20 Beta2): send failed for RemoteObject
Hello Aejaz, I am not getting why you are mentioning the complete URI path in endpoint, can't we avoid http://{server.name}:{server.port}/{context.root}/ Just say /messagebroker/amf the context root will take from the browser URL. channel-definition id=my-amf class=mx.messaging.channels.AMFChannel endpoint uri=http://{server.name}:{server.port}/{context.root}/messagebroker/a mf class=flex.messaging.endpoints.AMFEndpoint/ properties polling-enabledfalse/polling-enabled /properties /channel-definition Please correct if I am wrong. Thanks --Suresh Akula --- Peter Farland [EMAIL PROTECTED] wrote: Sorry, the J2EE context root as it would appear in the URL (i.e. this value will replace the token {context.root} at compile time based on the value of --context-root). e.g. --context-root=/dev Note that the other two tokens in the endpoint URL, {server.name} and {server.port} will be known at runtime if the SWF is loaded via a URL so these are replaced at runtime based on how the SWF is loaded. -Original Message- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of aejaz_98 Sent: Tuesday, April 25, 2006 3:12 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: (Flex20 Beta2): send failed for RemoteObject Thanks Peter. Please let me know how exactly to do that. Do you mean add --context.root C:\tomcat\webapps\flex while starting tomcat i.e. catalina start --context.root C:\tomcat\webapps\flex Is that right ? Thanks, Aejaz --- In flexcoders@yahoogroups.com, Peter Farland [EMAIL PROTECTED] wrote: Ah, yes, you need to specify --context.root on the command line as the client can't tell what the context root is (i.e. because you can have the default context root it can't make assumptions as to whether the first level under the webroot is a subdirectory or a context root). -Original Message- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of aejaz_98 Sent: Tuesday, April 25, 2006 1:59 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: (Flex20 Beta2): send failed for RemoteObject 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 sourcesamples.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/a mf class=flex.messaging.endpoints.AMFEndpoint/ properties polling-enabledfalse/polling-enabled /properties /channel-definition Thanks, Aejaz --- In flexcoders@yahoogroups.com, aejaz_98 aejaz_98@ 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
Re: [flexcoders] Re: (Flex20 Beta2): send failed for RemoteObject
As per the below code change the endpoint to endpoint uri=../messagebroker/amf class=flex.messaging.endpoints.AMFEndpoint/ as the URL to which I go form the browser is http://localhost:8080/flex/SimpleRemoteObject/SimpleRemoteObject.html from the URL it takes the http://localhost:8080/flex and it will append to ../ in uri. please let me know if you find any other alternative. --Suresh Akula --- aejaz_98 [EMAIL PROTECTED] wrote: Hi Peter, Thanks for taking the time to patiently answer my questions. Unfortunately, I am still unable to proceed. I changed the following line(in flex-enterprise-services.xml under channel definition for my-amf), endpoint uri=http://{server.name}:{server.port}/{context.root}/messagebroker/amf\ class=flex.messaging.endpoints.AMFEndpoint/ to endpoint uri=http://{server.name}:{server.port}/flex/messagebroker/amf class=flex.messaging.endpoints.AMFEndpoint/ as the URL to which I go form the browser is http://localhost:8080/flex/SimpleRemoteObject/SimpleRemoteObject.html there is no change in behavior. I must have not understood you correctly. Can you please clarify if possible on how to set context root step by step. Thanks again, Aejaz --- In flexcoders@yahoogroups.com, Peter Farland [EMAIL PROTECTED] wrote: Sorry, the J2EE context root as it would appear in the URL (i.e. this value will replace the token {context.root} at compile time based on the value of --context-root). e.g. --context-root=/dev Note that the other two tokens in the endpoint URL, {server.name} and {server.port} will be known at runtime if the SWF is loaded via a URL so these are replaced at runtime based on how the SWF is loaded. -Original Message- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of aejaz_98 Sent: Tuesday, April 25, 2006 3:12 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: (Flex20 Beta2): send failed for RemoteObject Thanks Peter. Please let me know how exactly to do that. Do you mean add --context.root C:\tomcat\webapps\flex while starting tomcat i.e. catalina start --context.root C:\tomcat\webapps\flex Is that right ? Thanks, Aejaz --- In flexcoders@yahoogroups.com, Peter Farland pfarland@ wrote: Ah, yes, you need to specify --context.root on the command line as the client can't tell what the context root is (i.e. because you can have the default context root it can't make assumptions as to whether the first level under the webroot is a subdirectory or a context root). -Original Message- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of aejaz_98 Sent: Tuesday, April 25, 2006 1:59 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: (Flex20 Beta2): send failed for RemoteObject 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 sourcesamples.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/a mf class=flex.messaging.endpoints.AMFEndpoint/ properties polling-enabledfalse/polling-enabled /properties /channel-definition Thanks, Aejaz --- In flexcoders@yahoogroups.com, aejaz_98 aejaz_98@ 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 === message truncated
RE: [flexcoders] Re: (Flex20 Beta2): send failed for RemoteObject
Are you loading your SWF from http://localhost:8080? Or are you using the standalone player by, say, double clicking on the SWF and opening it using SAFlashPlayer.exe? Note that if the SWF isn't loaded from the same domain then you'll need a crossdomain.xml file in the webroot of the domain that you're trying to access (i.e. localhost:8080). Pete From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of aejaz_98Sent: Tuesday, April 25, 2006 4:06 PMTo: flexcoders@yahoogroups.comSubject: [flexcoders] Re: (Flex20 Beta2): send failed for RemoteObject Hi Peter,Thanks for taking the time to patiently answer my questions. Unfortunately, I am still unable to proceed. I changed the following line(in flex-enterprise-services.xml under channel definition for my-amf),endpoint uri="http://{server.name}:{server.port}/{context.root}/messagebroker/amf" class="flex.messaging.endpoints.AMFEndpoint"/toendpoint uri="http://{server.name}:{server.port}/flex/messagebroker/amf" class="flex.messaging.endpoints.AMFEndpoint"/as the URL to which I go form the browser is http://localhost:8080/flex/SimpleRemoteObject/SimpleRemoteObject.html there is no change in behavior. I must have not understood you correctly. Can you please clarify if possible on how to set context root step by step.Thanks again,Aejaz--- In flexcoders@yahoogroups.com, "Peter Farland" [EMAIL PROTECTED] wrote: Sorry, the J2! EE context root as it would appear in the URL (i.e. this value will replace the token {context.root} at compile time based on the value of --context-root). e.g. --context-root=/dev Note that the other two tokens in the endpoint URL, {server.name} and {server.port} will be known at runtime if the SWF is loaded via a URL so these are replaced at runtime based on how the SWF is loaded. -Original Message- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of aejaz_98 Sent: Tuesday, April 25, 2006 3:12 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: (Flex20 Beta2): send failed for RemoteObject Thanks Peter. Please let me know how exactly to do that. Do you mean add --context.root C:\tomcat\webapps\flex while starting tomcat i.e. catalina start --context! .root C:\tomcat\webapps\flex Is that right ? Thanks, Aejaz --- In flexcoders@yahoogroups.com, "Peter Farland" pfarland@ wrote: Ah, yes, you need to specify --context.root on the command line as the client can't tell what the context root is (i.e. because you can have the default context root "" it can't make assumptions as to whether the first level under the webroot is a subdirectory or a context root). -Original Message- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of aejaz_98 Sent: Tuesday, April 25, 2006 1:59 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: (Flex20 Beta2): send failed for RemoteObjectThe detailed error message in this case is, Channel.Connect.Failed error<B! r> Netconnection.Call.Failed:HTTP:FailedMy flex-remoting-service.xml looks as follows, default-channels channel ref="my-amf"/ /default-channelsdestination id="EchoString" properties sourcesamples.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/a mf " class="flex.messaging.e! ndpoints.AMFEndpoint"/ proper! ties polling-enabledfalse/polling-enabled /properties /channel-definition Thanks, Aejaz--- In flexcoders@yahoogroups.com, "aejaz_98" aejaz_98@ 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 overlookedsomething obvious. Thanks, Aejaz ?xml version="1.0" encoding="utf-8"? mx:Application xmlns:mx="http://www.ado! be.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:statesmx:State name="TargetState" mx:RemoveChild child="{button1}"/! ; mx:RemoveChild child="
RE: [flexcoders] Re: (Flex20 Beta2): send failed for RemoteObject
No, you shouldn't need a crossdomain.xml file in this case. So long as you're sure that you're recompiling with the updated configuration each time that you make a change, and so long as this files contents matches what is on the server, and so long as you've tried replacing tokens with hard coded values and worked back to make sure they're not the problem, then an unrelated error must have happened during startup as the MessageBroker AMFChannel endpoint mustn't be active? To get more information on the client, you can add the following tag to your MXML: mx:TraceTarget level=0 / All of the traffic for your RPC services (like RemoteObject) will be traced out to the debug player log file, that is, the flashlog.txt file in your user directory (on Windows, C:\Documents and Settings\yourusername\flashlog.txt) so long as you have a mm.cfg file setup in this user directory with the following contents: ErrorReportingEnable=1 TraceOutputFileEnable=1 (Note the format of this C:\Documents and Settings\yourusername\mm.cfg file needs to be exact, no tabs or indents, etc). To get more information on the server, check your logs for stacktraces and other errors starting up the MessageBroker Servlet. For an example of what might go wrong, just say you have a messaging service include defined in your flex-enterprise-services.xml file and it included a JMS Adapter then Tomcat might not startup as it doesn't have the necessary support in a default installation... in which case you'd comment out the include for the message service. You can also change the logging settings in /WEB-INF/flex/flex-enterprise-services.xml to the Debug level and then look at the logs again for more clues. -Original Message- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of aejaz_98 Sent: Tuesday, April 25, 2006 6:20 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: (Flex20 Beta2): send failed for RemoteObject Thanks Peter, I am loading the SWF from the following URL, http://localhost:8080/flex/SimpleRemoteObject/SimpleRemoteObject.html Do I still need crossdomain.xml as Tomcat is running locally. If so what will this file contain in which directory I should create it. Thanks, Aejaz --- In flexcoders@yahoogroups.com, Peter Farland [EMAIL PROTECTED] wrote: Are you loading your SWF from http://localhost:8080? Or are you using the standalone player by, say, double clicking on the SWF and opening it using SAFlashPlayer.exe? Note that if the SWF isn't loaded from the same domain then you'll need a crossdomain.xml file in the webroot of the domain that you're trying to access (i.e. localhost:8080). Pete From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of aejaz_98 Sent: Tuesday, April 25, 2006 4:06 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: (Flex20 Beta2): send failed for RemoteObject Hi Peter, Thanks for taking the time to patiently answer my questions. Unfortunately, I am still unable to proceed. I changed the following line(in flex-enterprise-services.xml under channel definition for my-amf), endpoint uri=http://{server.name}:{server.port}/{context.root}/messagebroker/a mf class=flex.messaging.endpoints.AMFEndpoint/ to endpoint uri=http://{server.name}:{server.port}/flex/messagebroker/amf class=flex.messaging.endpoints.AMFEndpoint/ as the URL to which I go form the browser is http://localhost:8080/flex/SimpleRemoteObject/SimpleRemoteObject.html there is no change in behavior. I must have not understood you correctly. Can you please clarify if possible on how to set context root step by step. Thanks again, Aejaz --- In flexcoders@yahoogroups.com, Peter Farland pfarland@ wrote: Sorry, the J2! EE context root as it would appear in the URL (i.e. this value will replace the token {context.root} at compile time based on the value of --context-root). e.g. --context-root=/dev Note that the other two tokens in the endpoint URL, {server.name} and {server.port} will be known at runtime if the SWF is loaded via a URL so these are replaced at runtime based on how the SWF is loaded. -Original Message- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of aejaz_98 Sent: Tuesday, April 25, 2006 3:12 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: (Flex20 Beta2): send failed for RemoteObject Thanks Peter. Please let me know how exactly to do that. Do you mean add --context.root C:\tomcat\webapps\flex while starting tomcat i.e. catalina start --context! .root C:\tomcat\webapps\flex Is that right ? Thanks, Aejaz --- In flexcoders@yahoogroups.com, Peter Farland pfarland@ wrote: Ah, yes, you need to specify --context.root on the command line as the client can't tell what the context root is (i.e. because you can have the default