On 6/20/06, Peter Farland <[EMAIL PROTECTED]> wrote:
This is what is in the properties > flex compiler > additional compiler arguments
-services "C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\uploadServer\WEB-INF\flex\flex-enterprise-services.xml" -locale en_US
The path above is a valid path to my flex-enterprise-services.xml file.
It looks like they do. This is right out of samples and I just pasted it into my code.
<endpoint uri="http://{server.name }:{server.port}/{context.root}/messagebroker/amf" class="flex.messaging.endpoints.AMFEndpoint"/>
The bad news is I changed it to the below line just to see if I could get it working.
<endpoint uri=" http://localhost:8080/uploadServer/messagebroker/amf" class="flex.messaging.endpoints.AMFEndpoint"/>
It didnt work.
So now I am wondering if uploadServer isnt my context.root. It is the name of my webapp. Perhaps these are not the same thing.
I did stick this in, but could you tell me where flashlog.txt is kept?
Thanks
Hank
Hank:1. Are you compiling with a reference to the services configuration file? Either through a --services command line option to mxmlc (or a compiler services element in flex-config.xml)?
This is what is in the properties > flex compiler > additional compiler arguments
-services "C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\uploadServer\WEB-INF\flex\flex-enterprise-services.xml" -locale en_US
The path above is a valid path to my flex-enterprise-services.xml file.
2. Do any of your channel endpoints use a {context.root} token? If so, have you specified a --context-root command line option to mxmlc?
It looks like they do. This is right out of samples and I just pasted it into my code.
<endpoint uri="http://{server.name }:{server.port}/{context.root}/messagebroker/amf" class="flex.messaging.endpoints.AMFEndpoint"/>
The bad news is I changed it to the below line just to see if I could get it working.
<endpoint uri=" http://localhost:8080/uploadServer/messagebroker/amf" class="flex.messaging.endpoints.AMFEndpoint"/>
It didnt work.
So now I am wondering if uploadServer isnt my context.root. It is the name of my webapp. Perhaps these are not the same thing.
3. Can you add a <mx:TraceTarget level="0" /> to your MXML and then watch the flashlog.txt for more info?
I did stick this in, but could you tell me where flashlog.txt is kept?
Thanks
Hank
Pete
From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of hank williams
Sent: Tuesday, June 20, 2006 3:02 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Re: remoteObject send failingWell, that is a much cleaner call, but it still does the same thing :(
Hank
On 6/20/06, Doug Lowder <[EMAIL PROTECTED] > wrote:Hi Hank,
You should be able to call your RemoteObject method directly. See
if the following works:
<mx:Button label="get chart data"
click="chartTemplate.findCharts(1)" />
- Doug
--- In flexcoders@yahoogroups.com , "hank williams" <[EMAIL PROTECTED]>
wrote:
>
> I am trying to get remoteObjects up and running, talking to a FDS.
>
> I use mxml binding, and when I actually make the send() call to my
> remote object it generates an error "send failed". It does not
appear
> that the message is ever getting to the server because there is no
> traffic on the java console. If it was a bad destination or method
> name I would think that would require asking the server, which it
> doesnt seem to do.
>
> The error generated is just "send failed".
>
> So I suspect I am doing something bone headed on the client side
but
> dont know what. Below is the failing app.
>
> Any help appeciated.
>
> Hank
>
>
> <?xml version="1.0" encoding="utf-8"?>
> <mx:Application xmlns:mx=" http://www.adobe.com/2006/mxml "
layout="absolute">
>
> <mx:Script>
> <![CDATA[
> import mx.controls.Alert;
> ]]>
> </mx:Script>
>
> <mx:RemoteObject
> id = "chartTemplate"
> destination = "charts">
>
> <mx:method
> name="findCharts"
> result
= "dgChartTemplate.dataProvider=event.result"
> fault = " Alert.show
(event.fault.faultstring,'Error');" >
> <mx:arguments>
> <chartTemplateID>
> 1
> </chartTemplateID>
> </mx:arguments>
> </mx:method>
> </mx:RemoteObject>
>
> <mx:DataGrid x="20" y="80" id="dgChartTemplate" width="400">
> <mx:columns>
> <mx:DataGridColumn headerText="c1"
dataField="name"/>
> <mx:DataGridColumn headerText="c1"
dataField="time_interval"/>
> </mx:columns>
> </mx:DataGrid>
>
> <mx:Button label="get chart data"
> click = "chartTemplate.findCharts.send()"/>
> </mx:Application>
>
------------------------ Yahoo! Groups Sponsor --------------------~-->
Yahoo! Groups gets a make over. See the new email design.
http://us.click.yahoo.com/XISQkA/lOaOAA/yQLSAA/nhFolB/TM
--------------------------------------------------------------------~->
--
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
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
__._,_.___
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
Web site design development | Computer software development | Software design and development |
Macromedia flex | Software development best practice |
YAHOO! GROUPS LINKS
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.