Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle JMS priority header #234

Closed
christophd opened this Issue Apr 19, 2017 · 0 comments

Comments

Projects
None yet
1 participant
@christophd
Copy link
Member

christophd commented Apr 19, 2017

JMS priority header field is mapped to "priority" header in Citrus. Should be mapped to "citrus_jms_priority" in order to meet standard way of accessing Citrus internal JMS headers during validation.

@christophd christophd added this to the v2.7.2 milestone Apr 19, 2017

@christophd christophd added IN PROGRESS and removed READY labels Apr 19, 2017

@christophd christophd self-assigned this Apr 19, 2017

christophd added a commit that referenced this issue Apr 19, 2017

@christophd christophd closed this Apr 19, 2017

@christophd christophd removed the IN PROGRESS label Apr 19, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.