[OASIS Issue Tracker] (AMQPBINDMAP-28) Decide and document how to handle vendor properties for content-type and content-encoding

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Steve Huston created AMQPBINDMAP-28:
---------------------------------------

             Summary: Decide and document how to handle vendor properties for content-type and content-encoding
                 Key: AMQPBINDMAP-28
                 URL: https://issues.oasis-open.org/browse/AMQPBINDMAP-28
             Project: OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-BINDMAP) TC
          Issue Type: Bug
          Components: JMS Mapping
    Affects Versions: wd06
            Reporter: Steve Huston
            Assignee: Robert Gemmell


Came from large discussion around wd6 section 4 on 06-October-2015. What are the valid combinations for content type and encoding, does the JMS client act on them or report them, how to design such that a non-JMS and a JMS participant can communicate common use cases (e.g. text message, in json or xml format).




--
This message was sent by Atlassian JIRA
(v6.2.2#6258)