GitHub user binfalse opened a pull request:
https://github.com/apache/camel/pull/942
camel-twitter: remove truncation
This removes the non-effective truncation of messages to be sent to twitter.
See https://issues.apache.org/jira/browse/CAMEL-9850
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/binfalse/camel twitter-no-truncation
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/942.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #942
----
commit cbada76346fa0aae74128b2b74aa3a834144ea63
Author: Martin Scharm <mar...@binfalse.de>
Date: 2016-04-09T09:53:12Z
camel-xmpp: fix private chat response issue
Responding to a private chat wasn't able because the message was always
sent to
String participant = exchange.getIn().getHeader(XmppConstants.TO,
String.class);
However, the `XmppConstants.TO` in such messages is the camel instance
(which received the message) and not the chat's other participant.
Thus, responding to a chat message always resultet in a message to itself.
This patch fixes that issue and addresses messages always to
String participant = endpoint.getParticipant();
commit cb1b8f6337c4795fc9d5046c204ff1e5dc86d533
Author: Martin Scharm <mar...@binfalse.de>
Date: 2016-04-09T10:05:03Z
Merge branch 'master' of github.com:binfalse/camel
commit b31266e5b0f29c596288f1432a55445a60b4888b
Author: Martin Scharm <mar...@binfalse.de>
Date: 2016-04-10T08:33:17Z
Merge github.com:apache/camel
commit b96035b239974e3ddf4cb1c9a84258e11b9a1433
Author: Martin Scharm <mar...@binfalse.de>
Date: 2016-04-10T08:36:52Z
camel-twitter: removed the truncation
Twitter status updates were truncated to 160 chars if they were longer.
However the twitter limit is 140 chars, so this truncation didn't have
any effect and I removed it.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
