[
http://jira.jboss.com/jira/browse/JBMESSAGING-740?page=comments#action_12... ]
Ovidiu Feodorov commented on JBMESSAGING-740:
---------------------------------------------
Part of this task is to fix the fact that the new failover update map code does not use
MessagingMarshallable to transport it's data from server to client, so won't be
able to be versioned.
CallbackManager:
if (parameter instanceof MessagingMarshallable)
{
MessagingMarshallable mm = (MessagingMarshallable)parameter;
...
}
else if (parameter instanceof ConnectionFactoryUpdateMessage)
{
...
This was JBMESSAGING-764, which I'll close to reduce the clutter.
Make sure wireformat is just right
----------------------------------
Key: JBMESSAGING-740
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-740
Project: JBoss Messaging
Issue Type: Task
Affects Versions: 1.2.0.Beta1
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.2.0.CR1
We need to get the wireformat exactly right before the 1.2 release since changing it
aftwerwards is going to give compatibility issues.
We should analyse it and make sure it is exactly correct.
Suggestion would be to provide a custom wire format for all invocations, not just the few
we currently have so we don't rely on java/jboss serialization.
Also wireformat for ping
--
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