[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1167) Store the reference to the object instead of serializing object upon JBossObjectMessage.setObject.

[Tim Fox (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1167?page=comments#action_12389869 ] 
            
Tim Fox commented on JBMESSAGING-1167:
--------------------------------------

We serialize the object since the JMS spec states that changing the body of a received message shouldn't affect the sent message, even in VM:

JMS 1.1 spec Section 3.9:

"After sending a message, a client may retain and modify it without affecting
the message that has been sent. The same message object may be sent multiple
times."

If we were to just pass a Java reference we wouldn't be able to guarantee that.

> Store the reference to the object instead of serializing object upon JBossObjectMessage.setObject.
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1167
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1167
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.4.0.SP1
>            Reporter: Jay Howell
>         Assigned To: Tim Fox
>
> Object Serialization happens in the JBossObjectMessage.setObject  and then the reference to the object is set to null.  This means that if you are delivering messages within the same JVM, the objects still have to go through serialization.  This request is to delay serialization until it needs to be sent across the wire. 
> This is a performance optimization aimed at preventing unnecessary serialization.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira