"mwelss" wrote : | Looking at the code, the payload seems to be serialized, but on the producer I set the delivery-mode to non-persistent, so why | serialize anyway? It's all in one jboss, no cluster etc. |
This is required by the JMS spec. http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/jms/ObjectMessage.html ObjectMessage::setObject javadoc: Sets the serializable object containing this message's data. It is important to note that an ObjectMessage contains a snapshot of the object at the time setObject() is called; subsequent modifications of the object will have no effect on the ObjectMessage body. So we need to basically need to copy the message when it is set so if the user than changes the original object the object message is unchanged. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3946201#3946201 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3946201 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
