[SWS-798] Ensure that only valid Java Identifiers are added to JMS headers Created: 24/Sep/12  Updated: 02/Jul/13  Resolved: 25/Sep/12

Status: Resolved
Project: Spring Web Services
Component/s: None
Affects Version/s: None
Fix Version/s: 2.1.2

Type: Improvement Priority: Minor
Reporter: Mark Bromfield Assignee: Arjen Poutsma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 0.05d
Original Estimate: Not Specified

Issue Links:
is related to SWS-833 All JMS headers ignored, if the are n... Resolved


This is related to closed issue SWS-252. The mime header property that is returning an exception is "Accept-Encoding". Need a way to ensure that valid Java Identifiers are added to jms headers or somehow eliminated. The current implementation just returns the given header name if no match is found in the CONVERSION_TABLE and set into the message header.

Comment by Mark Bromfield [ 24/Sep/12 ]

The correct closed issue is SWS-258 not 252 as originally stated.

Comment by Arjen Poutsma [ 25/Sep/12 ]

Fixed. JmsTransportUtils now has a fallback mechanism for headers that are not in the conversion table.

Generated at Sun Oct 21 15:21:41 UTC 2018 using JIRA 7.9.2#79002-sha1:3bb15b68ecd99a30eb364c4c1a393359bcad6278.