camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shreyas Purohit (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-8265) Create a camel component that can Integrate with Hipchat
Date Wed, 28 Jan 2015 18:46:35 GMT

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

Shreyas Purohit commented on CAMEL-8265:
----------------------------------------

[~davsclaus] Can you please take a look at this component. I think this is a very useful component
to notify updates in Hipchat rooms. This would also allow to trigger a route by sending a
message on Hipchat. I have followed everything on wiki related to contributing new components.
If there is something more I need to do, I will do it.

> Create a camel component that can Integrate with Hipchat
> --------------------------------------------------------
>
>                 Key: CAMEL-8265
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8265
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Shreyas Purohit
>            Priority: Minor
>   Original Estimate: 30h
>  Remaining Estimate: 30h
>
> Hipchat (www.hipchat.com) is a tool that allows teams to chat and exchange messages.
Hipchat allows you to create room's where multiple users and talk and get notified upon events.
Hipchat provides v2 API as defined at https://www.hipchat.com/docs/apiv2/auth. The tokens
are called Personal Access Token in V2.
> Camel Hipchat Producer: It should be able to send message to a room and/or users. It
must be able to define the supported color, message formats and notification triggers as provided
by the API.
> Camel Hipchat Consumer: It should be able to consume the latest message from a given
set of users identified by mention name or email address. The message and the datetime of
the message should be passed as the exchange.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message