You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Brett Meyer (Created) (JIRA)" <ji...@apache.org> on 2012/01/07 07:49:39 UTC
[jira] [Created] (CAMEL-4873) camel-twitter: Twitter4J response
objects as Exchange body
camel-twitter: Twitter4J response objects as Exchange body
----------------------------------------------------------
Key: CAMEL-4873
URL: https://issues.apache.org/jira/browse/CAMEL-4873
Project: Camel
Issue Type: Improvement
Components: camel-twitter
Reporter: Brett Meyer
Priority: Minor
camel-twitter originally used its own Class(es) as the Exchange body. Instead, allow it to simply reuse the Twitter4J response objects (Status, Tweet, DirectMessage, etc.). This will provide applications the complete set of fields and require no maintenance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4873) camel-twitter: Twitter4J response
objects as Exchange body
Posted by "Willem Jiang (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183095#comment-13183095 ]
Willem Jiang commented on CAMEL-4873:
-------------------------------------
Applied patch with thanks to Brett.
> camel-twitter: Twitter4J response objects as Exchange body
> ----------------------------------------------------------
>
> Key: CAMEL-4873
> URL: https://issues.apache.org/jira/browse/CAMEL-4873
> Project: Camel
> Issue Type: Improvement
> Components: camel-twitter
> Reporter: Brett Meyer
> Assignee: Willem Jiang
> Priority: Minor
> Attachments: camel-twitter_1-7-12_patch.txt
>
>
> camel-twitter originally used its own Class(es) as the Exchange body. Instead, allow it to simply reuse the Twitter4J response objects (Status, Tweet, DirectMessage, etc.). This will provide applications the complete set of fields and require no maintenance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-4873) camel-twitter: Twitter4J response
objects as Exchange body
Posted by "Brett Meyer (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Meyer updated CAMEL-4873:
-------------------------------
Attachment: camel-twitter_1-7-12_patch.txt
Changes complete -- patch attached.
> camel-twitter: Twitter4J response objects as Exchange body
> ----------------------------------------------------------
>
> Key: CAMEL-4873
> URL: https://issues.apache.org/jira/browse/CAMEL-4873
> Project: Camel
> Issue Type: Improvement
> Components: camel-twitter
> Reporter: Brett Meyer
> Priority: Minor
> Attachments: camel-twitter_1-7-12_patch.txt
>
>
> camel-twitter originally used its own Class(es) as the Exchange body. Instead, allow it to simply reuse the Twitter4J response objects (Status, Tweet, DirectMessage, etc.). This will provide applications the complete set of fields and require no maintenance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-4873) camel-twitter: Twitter4J response
objects as Exchange body
Posted by "Willem Jiang (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-4873.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.10
> camel-twitter: Twitter4J response objects as Exchange body
> ----------------------------------------------------------
>
> Key: CAMEL-4873
> URL: https://issues.apache.org/jira/browse/CAMEL-4873
> Project: Camel
> Issue Type: Improvement
> Components: camel-twitter
> Reporter: Brett Meyer
> Assignee: Willem Jiang
> Priority: Minor
> Fix For: 2.10
>
> Attachments: camel-twitter_1-7-12_patch.txt
>
>
> camel-twitter originally used its own Class(es) as the Exchange body. Instead, allow it to simply reuse the Twitter4J response objects (Status, Tweet, DirectMessage, etc.). This will provide applications the complete set of fields and require no maintenance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-4873) camel-twitter: Twitter4J response
objects as Exchange body
Posted by "Willem Jiang (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned CAMEL-4873:
-----------------------------------
Assignee: Willem Jiang
> camel-twitter: Twitter4J response objects as Exchange body
> ----------------------------------------------------------
>
> Key: CAMEL-4873
> URL: https://issues.apache.org/jira/browse/CAMEL-4873
> Project: Camel
> Issue Type: Improvement
> Components: camel-twitter
> Reporter: Brett Meyer
> Assignee: Willem Jiang
> Priority: Minor
> Attachments: camel-twitter_1-7-12_patch.txt
>
>
> camel-twitter originally used its own Class(es) as the Exchange body. Instead, allow it to simply reuse the Twitter4J response objects (Status, Tweet, DirectMessage, etc.). This will provide applications the complete set of fields and require no maintenance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira