[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1167) Store the reference to the object instead of serializing object upon JBossObjectMessage.setObject.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1167?page=comments#action_1... ]
P Duffy commented on JBMESSAGING-1167:
--------------------------------------
Thanks for that Tim.
Let me run it back at you to be sure I understand the caveat. When we use this
"local VM object ref" feature, it would be wise to destroy the message
immediately after send to avoid any misadvertant change to the message, correct?
P.S. When do you anticipate 2.0 Beta to be available? And will 2.0 be shipping with EAP
5.0?
Cheers
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
Fix For: 2.0.0 Beta
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