On Mon, Sep 30, 2013 at 10:15 AM, anirbanroysap <[email protected]> wrote: > Hi Claus, > > Yes I have seen the example. > The twitter endpoint requires some configuration parameters like > consumerKey,accesToken etc. to be set. > If I understand correctly it can be set while creating the endpoint URL. > > So, can I declare my endpoint as > <endpoint id="mytwitter" > url="twitter://search?type=polling&delay=5&keywords=obama"> > <property name="consumerKey" value="XXXXXX"/> > <property name="consumerSecret value="XXXXXX"/> > <property name="accessToken" value="XXXXXX"/> > <property name="accessTokenSecret" value="XXXXXX"/> > </endpoint> >
You cannot do this, as <endpoint> does not support <property>. Though its a nice idea. > And then use it in my route as: > <to uri="mytwitter"/> > > Thanks and regards, > Anirban > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Consuming-camel-twitter-component-tp5740432p5740462.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
