This content has been marked as final. Show 4 replies
Does your HessianChannel subclass another Channel implementation?
Yes, it subclasses Channel, but I also tried with HTTPChannel, unfortunately I couldn't override the AFMXDecode and Encode to adapt it ... if I could that would've solved all the troubles
RemoteObject on the client doesn't do a whole lot, I would suspect that it's
your custom Channel does not set the right flags to make the ChannelSet think
that it successfully connected on the first request?
Can you add an event listener to your RemoteObject's ChannelSet (accessible
via its channelSet property) and listen for channelFault events?
I've added a TraceTarget to the main MXML this is what I get
'core-services' channel endpoint set to http://pc3:8080/remoting/Services
'8F17263B-CDAB-BCAB-0634-B93F8D347453' producer set destination to 'core-services'.
'8F17263B-CDAB-BCAB-0634-B93F8D347453' producer sending message 'D2B42D6E-4D55-37AF-ED77-B93F8D34C30B'
'core-services' channel is connected.
'core-services' channel sending message:
body = (Array)#1
clientId = (null)
destination = "core-services"
headers = (Object)#2
messageId = "D2B42D6E-4D55-37AF-ED77-B93F8D34C30B"
operation = "login"
source = (null)
timestamp = 0
timeToLive = 0
'8F17263B-CDAB-BCAB-0634-B93F8D347453' producer connected.
'8F17263B-CDAB-BCAB-0634-B93F8D347453' producer acknowledge of 'D2B42D6E-4D55-37AF-ED77-B93F8D34C30B'.
---- This is end of the first call on the service ----
--- and this is a trace after I push a button for another call ---
'8F17263B-CDAB-BCAB-0634-B93F8D347453' producer sending message 'C3961123-04D1-8A2A-5C6D-B93FEFFFD51E'
--- And nothing after this ----
the ChannelFaultEvent.FAULT .. event on ChannelSet is never fired