"kurt.stam(a)jboss.com" wrote : It looks like we copied the JMS message types of:
BytesMessage, MapMessage, ObjectMessage, StreamMessage and TextMessage
|
Not quite. There's no StreamMessage.
anonymous wrote :
| I see the following issues with the current implementation:
|
| 1. There are no interfaces for them in our implementation, so our Message
| will not actually 'be' one of these types. You'll have to do
Message.getPayload() and then figure out what type this it by using getInstanceOf().
|
There's no such operation Message.getPayload. You mean Payload.getPayload, I think.
But yes, that's essentially correct. Without changing interfaces to existing
infrastructure (and potentially breaking existing deployments), these simply represent
different views on to the underlying Message Body contents.
anonymous wrote :
| 2. We have left the old body implementation, so we have a body and a payload-body as I
understand it. This is confusing. I mean I can still do msg.getBody.add("kurt",
"Stam") and ignore the new payload stuff.
|
We cannot remove Body because it is the underlying Message structure that supports more
than any of these views allow. It's more powerful. These are simplifications for users
who know they only want to send text, Serialized objects etc.
anonymous wrote :
| 3. CommandMessage is listed at the same level as BytesMessage, but I think a
CommandMessage is more at the ESB logical level. It has nothing to do with the
implementation of the message. Maybe we can simple add
| a Message.property of MESSAGE_TYPE for this? No need to have a different API for this
type of message.
|
Possibly. It's just another simplification view. At present it supports type (what
type of CommandMessage) and a serialized object. Since we don't have any of these
CommandMessage implementations yet, it's hard to argue for or against.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070488#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...