activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-230) Allow setting STOMP content-type header via JMS
Date Fri, 25 Sep 2015 16:10:04 GMT


ASF GitHub Bot commented on ARTEMIS-230:

GitHub user jscheid opened a pull request:

    [WIP] ARTEMIS-230 Copy STOMP content-header back and forth

    This is incomplete, haven't really tested it yet. I'm just opening this PR so we can start
discussing the implementation.

You can merge this pull request into a Git repository by running:

    $ git pull ARTEMIS-230-STOMP-content-type

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #178


> Allow setting STOMP content-type header via JMS
> -----------------------------------------------
>                 Key: ARTEMIS-230
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Stomp
>            Reporter: Julian Scheid
>            Priority: Minor
> It's currently impossible to set the STOMP {{content-type}} header on JMS messages because
{{content-type}} is not a valid JMS property name. There should be some mechanism that allows
setting STOMP headers even when they don't match the JMS specification, at least for basic
STOMP headers like {{content-type}}.

This message was sent by Atlassian JIRA

View raw message