OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

amqp-bindmap message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (AMQPBINDMAP-25) How to handle certain property characteristics

    [ https://issues.oasis-open.org/browse/AMQPBINDMAP-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=66065#comment-66065 ] 

Robert Gemmell commented on AMQPBINDMAP-25:

As discussed at the meeting on April 24th, work in this area isn't inherent to JMS and supporting it over AMQP and so wont be covered in the mapping document, instead being treated as implementation detail/behaviour a particular JMS provider might have and document accordingly.

Leaving the JIRA open for now to address any fixups in the mapping document.

> How to handle certain property characteristics
> ----------------------------------------------
>                 Key: AMQPBINDMAP-25
>                 URL: https://issues.oasis-open.org/browse/AMQPBINDMAP-25
>             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
>            Priority: Blocker
> In section 3.3.3, pg 22/32, there's a TODO:
> TODO (intent): how to handle receiving the following:
> • String property names which do not conform with the JMS restrictions on naming
> • property values with types not defined in the JMS specification

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]