Mantis - Hessian
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2572 feature always 04-04-08 07:30 07-11-08 09:06
Reporter: bdespres Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: closed Product Version: 3.1.5  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 3.1.6  
Summary: 0002572: Hessian/Flex: hessian.client.HessianMessage never sets its messageId
Description: I've been adding some debug/logging to my application to track messages sent and received, but it's hard to line them up because HessianMessage never sets a unique messageId (it's always null).

If HessianMessage just extended mx.messaging.message.AbstractMessage instead of implementing IMessage, it would pick up the code that sets the Id. In fact, the whole class would just boil down to this:

package hessian.client
{
  import mx.messaging.messages.AbstractMessage;

  internal class HessianMessage extends AbstractMessage
  {
    public function HessianMessage(body:Object, destination:String)
    {
        this.body = body;
        this.destination = destination;
    }
}

I've been running my app with this change (using Flex 2.0.1) and it seems to work ok.
Steps To Reproduce:
Additional Information: See http://opensource.adobe.com/svn/opensource/flex/sdk/tags/3.0.0.477/frameworks/projects/rpc/src/mx/messaging/messages/AbstractMessage.as [^]

Notice that that "function get messageId()" assigns a uuid to the messageId if none was set before.
Relationships
Attached Files:

There are no notes attached to this issue.