Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <7530066.92841293907797398.JavaMail.jira@thor>
Date: Sat, 1 Jan 2011 13:49:57 -0500 (EST)
From: =?utf-8?Q?Christian_M=C3=BCller_=28JIRA=29?= <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Resolved: (CAMEL-3475) Idenitify incoming message type in
 camel-smpp consumer
In-Reply-To: <14311411.82251293801465154.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CAMEL-3475?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian M=C3=BCller resolved CAMEL-3475.
-------------------------------------

    Resolution: Fixed

> 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=C3=BCller
>             Fix For: 2.6.0
>
>
> We need a way to identify an incoming message type from a camel-smpp cons=
umer.
> Currently there is no clear indication if the incoming message is SMS, a =
delivery notification or an alert notification, as all these messages are c=
onverted to a camel SmppMessage.
> We could add an additional header to the exchange to identify the message=
 type, or add an attribute to SmppMessage?

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.