Problem solved.
Well I really learned how to debug stuff here, but the
problem was dumb.
You cant have two flex webapps in the webapps folder.
At some point in this process (hours ago) I had figured that out, and I had
removed the unpacked samples folder from webapps, but I had forgotten to remove
the samples.war file. This cause flex to be confused and was obviously reading
the wrong flex-enterrpise-services.xml file.
Thanks for all your help
Pete.
Hank.
On 6/20/06, hank
williams <[EMAIL PROTECTED]>
wrote:
<channel id="my-amf" type="
mx.messaging.channels.AMFChannel">
<endpoint uri="http://{
server.name}:{server.port}//messagebroker/amf"/>
<properties>
<polling-enabled>false</polling-enabled>
</properties>
</channel>
So the question is, where is it getting this from?
Hank
Ok, so we are getting
down to the nub of the problem.
this is what my
flex-enterprise-services.xml file says my channel definition
is:
<channel-definition
id="my-amf" class="mx.messaging.channels.AMFChannel ">
<properties>
<polling-enabled>false</polling-enabled>
</properties>
</channel-definition>
And this is what the debugger thinks it
is:
<channel id="my-amf"
type="mx.messaging.channels.AMFChannel">
<endpoint
uri="http://{
server.name}:{server.port}//messagebroker/amf"/>
<properties>
<polling-enabled>false</polling-enabled>
</properties>
</channel>
As you suggested in the last
email I did test the endpoint in the browser and
http://localhost:8080/uploadServer/messagebroker/amf is a
valid endpoint because I dont get the 500 error, the screen just goes
blank.
I also did a global search of the word "messagebroker" just to
see if there might be some conflicting definition. But there isnt. The only
place it is is where it should be. There is no other definition for my-amf.
Could there be some wierd caching issue since I recently changed the
endpoint to the hardcoded definition that it doesnt seem to be seeing.
Thanks
Hank
> 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.
[Pete] Try
browsing to the endpoint URI. If it's correct, it will not throw a 500
error and present a blank screen.
>> 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?
[Pete] You could
either debug with Flex Builder and it usually show trace output in the
console panel, though I usually launch SWFs from a variety of places so I
like to configure Flash Player trace logging manually. If you're on
Windows, then you need to have a mm.cfg file in your %HOMEDRIVE%%HOMEPATH%
directory, i.e. C:\Documents and
Settings\yourusername\mm.cfg
In here, the
contents should be:
ErrorReportingEnable=1
TraceOutputFileEnable=1
Then, assuming
you're using the debug versions of the Flash Player, a file called
flashlog.txt will be created in your user directory. (I use tail.exe from
cygwin to tail this file so that it appears as an updating console log).
Pete
