The project I'm working on is using Flex 3 (latest beta) and LCDS 
2.5.1 running under Tomcat 6.x. The service consists of a Java class 
and is correctly defined in the remoting-config.xml

All things work as they should. 

Now I want to move the project to a AIR application. I know how to 
setup an AIR application and moving from a working Flex 3 application 
to an AIR application is no big deal. 

The project compiles without problems and the -services directive 
points to the services-config.xml, the same one from the working Flex 
3 application. So one expect things to be alright but then things 
fall apart. As soon as the AIR application is launched and tries to 
connect to the destination, the following error occurs.

[FaultEvent fault=[RPC Fault faultString="Send failed" 
faultCode="Client.Error.MessageSend" 
faultDetail="Channel.Connect.Failed error NetConnection.Call.Failed: 
HTTP: Failed: url: 'http://oolWall_AIR.swf/coolwall/messagebroker/
amf'"] messageId="8E8E8B57-66F0-D797-2B5E-137734E88D9C" type="fault" 
bubbles=false cancelable=true eventPhase=2]

It is immediately obvious that the url is not correct. The host name 
and port is missing and even the first letter "C" is missing from
 .swf file name. It should have read http://localhost:8080/coolwall/
messagebroker/amf but apparently the AIR application is using the
 .swf file name minus the starting Capital character as the host name 
and port number. 

I use a program called ServiceCapture to capture the network chatter 
and it confirmed me that the host name and port number is indeed 
wrong. I mean it could also be a faulty debug trace statement but 
this proofs that the generated URL when using AIR and LCDS is wrong. 

In the Adobe Flex Builder Jira bug tracking system there is an issues 
which has been closed a couple of month ago and dismisses it as an 
error of either LCDS or AIR. The workaround is handcoding the exact 
URL in the remoting-config.xml file which is ofcourse not very 
sensible. I cannot judge which product is the one to blame as I lack 
the knowledge to do so. 

So does anyone (Adobe?) know which product (FB, AIR, LCDS?) is faulty 
and when it will be fixed. Thank you very much.

Reply via email to