[ 
https://issues.apache.org/jira/browse/CAMEL-6116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591398#comment-13591398
 ] 

Ioannis Alexandrakis edited comment on CAMEL-6116 at 3/2/13 12:38 PM:
----------------------------------------------------------------------

Yep sorry 'bout that, I didn't run the checkstyle (thanx for the info, just a 
missing space :P)... I attached a second patch. (No unit test though yet...)
                
      was (Author: i.alexandrakis):
    Yep sorry 'bout that, I didn't run the checkstyle -thanx for the info- 
(just a missing space :P)... I attached a second patch. (No unit test though 
yet...)
                  
> Populate all optional parameters from DeliverSm (if it is DeliveryReceipt)
> --------------------------------------------------------------------------
>
>                 Key: CAMEL-6116
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6116
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-smpp
>            Reporter: Ioannis Alexandrakis
>            Assignee: Christian Müller
>              Labels: optional, parameters
>             Fix For: 2.11.0
>
>         Attachments: enableOptParamsOnReceipts.java.patch, 
> enableOptParamsOnReceiptsv2.java.patch
>
>
> Hello all,
> I am currently working on a project requiring the use of camel-smpp. I 
> stumbled upon some problems integrating with the customer's SMSC, and I 
> modified the code of camel-smpp in order to fit my needs (just adding some 
> functionality though, not removing any).
> More specifically, for submitting a new message, the delivery receipt held 
> the corresponding submit_sm id in the optional parameters (as 
> receipted_message_id). With the current trunk code, I did not get the 
> optional parameters of the delivery receipt, so I could not match the 
> delivery receipt to the outgoing sms. As a solution I just looped all the 
> optional parameters and put them into a map as a header (and instead of 
> checking each optional parameter name, I just put whatever jsmpp was sending 
> back, so if someone wants to put other optional parameters to jsmpp too, they 
> would simply automatically be populated back in camel-smpp.)
> Please find the patch attached

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to