Sure you can check [1] for and example, thanks! [1] https://github.com/apache/camel/blob/b9a3117f19dd19abd2ea8b789c42c3e86fe4c488/components/camel-fhir/camel-fhir-component/src/test/java/org/apache/camel/component/fhir/FhirCustomClientConfigurationIT.java#L63
On Tue, Jun 25, 2019 at 7:42 AM Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > I have fixed this for master, eg Camel 3 > > On Fri, Jun 21, 2019 at 2:20 PM Claus Ibsen <claus.ib...@gmail.com> wrote: > > > > And btw you should still be able to configure them as query > > parameters, as those @UriParam etc are for documentation purposes. > > > > On Fri, Jun 21, 2019 at 2:19 PM Claus Ibsen <claus.ib...@gmail.com> > wrote: > > > > > > Hi > > > > > > Ah those 2 are wrong they should be @UriParam also. You are welcome to > > > log a JIRA and provide a PR > > > > > > On Fri, Jun 21, 2019 at 10:10 AM Paw B Sørensen > > > <paw.b.soren...@systematic.com> wrote: > > > > > > > > The camel fhir component supports setting several query parameters. > In the implementation of FhirConfiguration all of these parameters are > annotated with @UriParam. Also in the implementation of FhirConfiguration I > find the client and clientFactory variables but they are annotated with > @Metadata. Can I make my own custom implementation of the client to > > > > intercept whenever a response code 4xx is received? And is it > possible to set these Metadata values in my camel route? > > > > > > > > > > > > > -- > > > Claus Ibsen > > > ----------------- > > > http://davsclaus.com @davsclaus > > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > > > > -- > > Claus Ibsen > > ----------------- > > http://davsclaus.com @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
