Not applicable
10-07-2007
15:33 PDT
- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Hi Cato,
You're syntax is fine and you can listen at the service level
(flexComRO) or the operation level (flexComRO.LoginUser).
What is happening under the covers is that the RemoteObject's
underlying
Producer has ChannelSet. This ChannelSet loops through
pinging each of
its Channels until one responds successfully. If you have
more than one
channel defined for your RemoteObject destination it will
move on to the
next before failing outright.
However, you may also be experiencing a bug where say if the
Channel was
an AMFChannel, it's underlying flash.net.NetConnection may
not be
throwing an error? Or perhaps the bug is that he AMFChannel
is receivng
and error but not correctly dispatching the error?
You could try getting the channelSet off the RemoteObject
instance and
adding an event listener for a "channelFault" type of event.
What version of FDS or LCDS are you using? Could you open the
rpc.swc in
WinZip and look at catalog.xml and let us know what the
version
information says?
Pete
You're syntax is fine and you can listen at the service level
(flexComRO) or the operation level (flexComRO.LoginUser).
What is happening under the covers is that the RemoteObject's
underlying
Producer has ChannelSet. This ChannelSet loops through
pinging each of
its Channels until one responds successfully. If you have
more than one
channel defined for your RemoteObject destination it will
move on to the
next before failing outright.
However, you may also be experiencing a bug where say if the
Channel was
an AMFChannel, it's underlying flash.net.NetConnection may
not be
throwing an error? Or perhaps the bug is that he AMFChannel
is receivng
and error but not correctly dispatching the error?
You could try getting the channelSet off the RemoteObject
instance and
adding an event listener for a "channelFault" type of event.
What version of FDS or LCDS are you using? Could you open the
rpc.swc in
WinZip and look at catalog.xml and let us know what the
version
information says?
Pete
Views
Replies
0 Likes
Total Likes