Hi Yeah if the telegram has added new fields to their API then it sounds like that the camel-telegram component needs to have those added as well. You are welcome to create a JIRA and provide a PR.
On Thu, Jan 3, 2019 at 8:33 PM Gandhi, Vineet <[email protected]> wrote: > > Hi, > > I was testing the current supported features in the 3.0 SNAPSHOT release for > camel telegram component. > Use case : > > > 1. There is a telegram channel(private/public). > 2. camel telegram bot wants to write data to channel to consume from > channel. > > The above is failing as the JSON structure is updated with new field but POJO > Update.java is not updated. > > Json : > result": [ > { > "update_id": 219398823, > "channel_post": { > "message_id": 67, > "chat": { > "id": -1001245756934, > "title": "cameltemp", > "username": "cameltelegram", > "type": "channel" > }, > "date": 1546505413, > "text": "tedt" > } > } > ] > > Update.java : > > public class Update implements Serializable { > > > > private static final long serialVersionUID = -4001092937174853655L; > > > > @JsonProperty("update_id") > > private Long updateId; > > > > > > private IncomingMessage message; > } > > I have made the changes locally and tested with telegram account. Also added > junit for the above changes. > Should I raise a PR for this ? > > Regards, > Vineet > > > > This e-mail, including attachments, may include confidential and/or > proprietary information, and may be used only by the person or entity > to which it is addressed. If the reader of this e-mail is not the intended > recipient or his or her authorized agent, the reader is hereby notified > that any dissemination, distribution or copying of this e-mail is > prohibited. If you have received this e-mail in error, please notify the > sender by replying to this message and delete this e-mail immediately. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
