Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Unknown
Description
The camel twitter component parses the uri assuming the component has twitter as as scheme which is correct in most of the cases but could fail if one would pre-configure a number of twitter components:
<bean id="tw-account-1" class="rg.apache.camel.component.twitter.TwitterComponent"> <property name="accessToken" value="tokenForAccount1"/> </bean> <bean id="tw-account-2" class="rg.apache.camel.component.twitter.TwitterComponent"> <property name="accessToken" value="tokenForAccount2"/> </bean> <camelContext> <route> <from uri="tw-account-1:search"/> ... </rute> <route> <from uri="tw-account-2:timeline/mentions"/> ... </rute> <camelContext/>
Relevant code: