Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-10923

[QUICKSTART] camel-linkedin quickstart is not working

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • fuse-7.5-ER2
    • fuse-7.4-GA
    • Camel

    Description

      Camel-linkedin quickstart README says:

      Change your working directory to `camel-linkedin` directory.
* Run `mvn clean install` to build the quickstart.
* Start Red Hat Fuse 7 by running bin/fuse (on Linux) or bin\fuse.bat (on Windows).
* Create the following configuration file in the etc/ directory of your Red Hat Fuse installation:

  InstallDir/etc/org.jboss.fuse.quickstarts.camel.linkedin.cfg
  Edit the org.jboss.fuse.quickstarts.camel.linkedin.cfg file with a text editor and add the following contents:

  userName=<LinkedIn account user name>
  userPassword=<LinkedIn account password>
  accessToken=<LinkedIn access token>
  clientId=<LinkedIn client id>
  clientSecret=<LinkedIn client secret>

      When I do that I get following error:

      Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: linkedin://search/searchCompanies?consumer.delay=60&consumer.initialDelay=15&consumer.timeUnit=SECONDS&fields=%3A%28companies%3A%28name%2Ctwitter-id%2Cwebsite-url%29%29&keywords=Red+Hat due to: Property accessToken can not be defined if property userName is set
	at org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:758) ~[?:?]
	at org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:80) ~[?:?]
	at org.apache.camel.model.RouteDefinition.resolveEndpoint(RouteDefinition.java:219) ~[?:?]
	at org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:115) ~[?:?]
	at org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:121) ~[?:?]
	at org.apache.camel.model.FromDefinition.resolveEndpoint(FromDefinition.java:69) ~[?:?]
	at org.apache.camel.impl.DefaultRouteContext.getEndpoint(DefaultRouteContext.java:97) ~[?:?]
	at org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:1283) ~[?:?]
	at org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:204) ~[?:?]
	... 25 more
Caused by: java.lang.IllegalArgumentException: Property accessToken can not be defined if property userName is set

      This issue is caused by ENTESB-10368. New approach is using only access token. New instructions should be:

        InstallDir/etc/org.jboss.fuse.quickstarts.camel.linkedin.cfg
  Edit the org.jboss.fuse.quickstarts.camel.linkedin.cfg file with a text editor and add the following contents:

  accessToken=<LinkedIn access token>

      Attachments

        Issue Links

          is caused by

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-10368 camel-linkedin: If accessToken is set, other credentials should be unnecessary

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-11757 [QUICKSTART] camel-linkedin quickstart is not working

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users ENTESB-11060 [camel-linkedin] Support V2 of Linkedin API

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Feature Request - Feature requests from customers and/or users ENTESB-12056 Investigate Support V2 of Linkedin API

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              johnpoth John Poth
              jbouska@redhat.com Jan Bouska
              Jan Bouska Jan Bouska
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: