[CAMEL-8240] camel-apns should allow custom expiration times so that users get fine grained expiration control for mobile push messages

• Type: New Feature
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.14.1
• Fix Version/s: 2.14.2, 2.15.0
• Component/s: camel-apns
• Estimated Complexity: Novice
• Assignee: Willem Jiang
• Reporter: Justin Heesemann
• Created: 13/Jan/15 15:31
• Updated: 17/Jan/15 11:10
• Resolved: 17/Jan/15 11:10

Description

Currently it is not possible to send apns messages with a user defined expiration date.
This affects both STRING and PAYLOAD message types.
The org.apache.camel.component.apns.ApnsProducer calls the ApnsService.push(Collection<String> deviceTokens, String payload) throws NetworkIOException;
method which uses a EnhancedApnsNotification.MAXIMUM_EXPIRY (somewhen in 2038).

A possible solution would allow the usage of a new ApnsConstants.HEADER_EXPIRY message header where users could store the wanted expiration time.