Home

Questions?

  1. Properties?:
    The message properties are currently set at the body/payload level of the message.
    1. Should the properties be on a header? If they're here to "describe" the message body/payload (and nothing else), then I'd say leave it at the Message level (but what of the Payload.mimeHeaders then?). If it's more general message metadata, I'd go for adding it to the header.
    2. Does they need to support more than {@link String} based values?
    3. If a property value needs to be an Object, then is it really an attachement?
  2. Header?:
    There's currently no message "header". There's a possible argument that "if you have a body, then you must have a head/header". This is a rather academic point IMO. If it "must" have a head to go with the body, should we add legs and arms too ;-) ?

    At the end of the day, what would go into the header? Addressing info perhaps? By all accounts, items such as message context and message properties info need to reside at the same level as the message body/payload. If we have more than one thing to go into the header (even potentially), then I'd be all for it. But I wouldn't be adding it simply because we have a "body".

  3. Context and Call?:
    The existing message has Context and Call parts, but they're either empty or unused (as far as I can see). Shouldn't we add these when we support these features within the ESB as a whole, and not before? They're not represented in this Message interpretation.