0002572: Hessian/Flex: hessian.client.HessianMessage never sets its messageId

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0002572

[Hessian]

feature

always

04-04-08 07:30

07-11-08 09:06

Reporter

bdespres

View Status

public

Assigned To

Priority

normal

Resolution

fixed

Status

closed

Product Version

3.1.5

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.

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.

Attached Files

Relationships

There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
04-04-08 07:30	bdespres	New Issue
07-11-08 09:06	emil	Status	new => closed
07-11-08 09:06	emil	Resolution	open => fixed
07-11-08 09:06	emil	Fixed in Version	=> 3.1.6

Mantis 1.0.0rc3[^]

27 total queries executed.
25 unique queries executed.