Hi Danesh, In case there's no connector for a particular purpose, class mediators are always an option. You can write your own classes to connect, process, aggregate and store the response from the streaming API. Please use [1] and [2] as a reference for writing and integrating class mediators in a message flow. You can get these steps done in one proxy service.
As an additional step, you will have to define another proxy service to retrieve data stored by the first proxy service. I hope Twitter's streaming definition explains that further [below diagram]. [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/mediation/mediation-library/connectors/org.wso2.carbon.connector.twitter/1.0.0/src/main/java/org/wso2/carbon/connector/twitter/TwitterConfig.java [2] https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/mediation/mediation-library/connectors/org.wso2.carbon.connector.twitter/1.0.0/src/main/resources/twitter_config/init.xml Thanks, On Wed, Jul 2, 2014 at 10:07 AM, Danesh Kuruppu <[email protected]> wrote: > Hi All, > > $subject please? > > The Twitter Connector in WSO2 ESB uses the Twitter REST API. > Is it possible for me to connect Twitter Streaming API through ESB? > > Please help me. > > [1] https://dev.twitter.com/docs/api/streaming > > Thanks > > -- > > Danesh Kuruppu > Senior Software Engineer > WSO2 Inc, > Mobile: +94 (77) 1690552 > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Gayan Kaushalya Yalpathwala* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 71 8682704 <http://asia14.wso2con.com/> <http://asia14.wso2con.com/>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
