[
https://issues.apache.org/jira/browse/CAMEL-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976426#action_12976426
]
Christian Müller commented on CAMEL-3475:
-----------------------------------------
Workaround until Camel 2.6:
{code}
SmppMessage smppMessage = ...;
boolean isAlertNotification = smppMessage.getCommand() instanceof
AlertNotification;
boolean isDataSm = smppMessage.getCommand() instanceof DataSm;
boolean isDeliveryReceipt = smppMessage.getCommand() instanceof DeliverSm &&
((DeliverSm) smppMessage.getCommand())..isSmscDeliveryReceipt();
boolean isDeliverSm = smppMessage.getCommand() instanceof DeliverSm &&
!((DeliverSm) smppMessage.getCommand())..isSmscDeliveryReceipt();
{code}
> Idenitify incoming message type in camel-smpp consumer
> ------------------------------------------------------
>
> Key: CAMEL-3475
> URL: https://issues.apache.org/jira/browse/CAMEL-3475
> Project: Camel
> Issue Type: Improvement
> Components: camel-smpp
> Reporter: Jaco van Tonder
> Assignee: Christian Müller
> Fix For: 2.6.0
>
>
> We need a way to identify an incoming message type from a camel-smpp consumer.
> Currently there is no clear indication if the incoming message is SMS, a
> delivery notification or an alert notification, as all these messages are
> converted to a camel SmppMessage.
> We could add an additional header to the exchange to identify the message
> type, or add an attribute to SmppMessage?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
