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

[Jay Howell (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1167?page=comments#action_12390317 ] 
            
Jay Howell commented on JBMESSAGING-1167:
-----------------------------------------

Looks like 2.0 beta is not due out until 30/Jun/08 on the road map(http://jira.jboss.org/jira/secure/BrowseProject.jspa?id=12310061&subset=-1).  Just spoke to Tim and he said that EAP 5.0 will probably ship not with JBM 2.0, but with another 1.x version.  Unless the AS 5.0 or the EAP 5.0 slip their schedule, it will come out too soon for JBM 2.0.   So most likely JBM 2.0 will go into something like 5.1.  But the Beta will come out sooner than that. 

Jay:)

> 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