Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.22.1
-
None
Description
There has been a change in twitter APIs. On September 17^th^, twitter discontinued the legacy direct message endpoints.
There are three sendDirectMessage methods provided by twitter4j API.
DirectMessage | sendDirectMessage(long userId, java.lang.String text) Sends a new direct message to the specified user from the authenticating user. |
DirectMessage | sendDirectMessage(long userId, java.lang.String text, long mediaId) Sends a new direct message to the specified user from the authenticating user. |
DirectMessage | sendDirectMessage(java.lang.String screenName, java.lang.String text) Sends a new direct message to the specified user from the authenticating user. |
The first two methods use the new endpoints(direct_messages/events/new), while the third one uses the old APIs(direct_messages/new)
Camel twitter component uses the third method to send direct message (using screen name).
This needs to be changed in order to support direct message sending to twitter